Bug 321439 - [preferences] Allow whitespace options per content type
Summary: [preferences] Allow whitespace options per content type
Status: ASSIGNED
Alias: None
Product: Platform
Classification: Eclipse Project
Component: Text (show other bugs)
Version: 3.6   Edit
Hardware: All All
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Platform-Text-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-07-31 17:19 EDT by Eric Estievenart CLA
Modified: 2019-09-06 16:10 EDT (History)
2 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Eric Estievenart CLA 2010-07-31 17:19:18 EDT 
Build Identifier: 20100617-1415

Splitted from bug #257313

Users should be allowed to customize settings like whitespace
display, fonts, coloring, whatever..., for editors which do not have
proper defaults, without setting that globally.

The most painful is obviously (for me) not to have tabs displayed in a makefile
editor by default without displaying tabs,spaces, lfs in all lother editors.

Note :
1. This bug is not a CDT/Make bug. It is a global editor
configuration bug. 
2. I know it is likely to be requalified as an ER, but for me it
is really a severe missing functionality (or PITA), so logged as normal bug.


Reproducible: Always

Steps to Reproduce:
Just try to have tabs displayed in a makefile editor
without having the displayed for any other language.
Comment 1 Remy Suen CLA 2010-07-31 17:38:04 EDT 
Issues and concerns with text editors go to Platform Text.
Comment 2 Dani Megert CLA 2010-08-02 03:04:29 EDT 
Each editor can decide to override the defaults like e.g. the Java editor does. I treat this bug to offer whitespace settings per content type. If you need more/other options then please file separate bugs.
Comment 3 Eclipse Webmaster CLA 2019-09-06 16:10:33 EDT 
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.