Bug 98106 - [IDE] File properties do not list line delimiter
Summary: [IDE] File properties do not list line delimiter
Status: NEW
Alias: None
Product: Platform
Classification: Eclipse Project
Component: IDE (show other bugs)
Version: 3.1   Edit
Hardware: PC Linux-Motif
: P5 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Platform UI Triaged CLA
QA Contact:
URL:
Whiteboard:
Keywords: helpwanted
Depends on:
Blocks:
 
Reported: 2005-06-02 09:55 EDT by Douglas Pollock CLA
Modified: 2019-09-06 16:15 EDT (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Douglas Pollock CLA 2005-06-02 09:55:16 EDT
3.1 RC1, Motif, KDE 3.3.2, X.org 6.8.2, Linux 2.6.11

When the properties are opened on a project, both the file encoding and the line
delimiter are listed.  When the properties are opened on a file, only the file
encoding is listed.

It would be nice if the line delimiter were listed too.
Comment 1 Michael Van Meekeren CLA 2005-06-02 10:21:36 EDT
We would need to open the file to figure this out.  This has been mentioned by
Text, they would have to supply this information.
moving.
Comment 2 Dani Megert CLA 2005-06-02 10:40:11 EDT
That's already possible with Text API:
1. get the file buffer
2. get the document from the file buffer
3. get the line delimiter via TextUtilites.getDefaultLineDelimiter(IDocument)

This will give the default LD used by Platform Text. It does not report mixed
LDs. For this you'd have to iterate over each line using
ILineTracker.getLineDelimiter(int) until mixed LDs are detected or the end of
the document is reached.
Comment 3 Susan McCourt CLA 2009-07-15 12:06:37 EDT
"As per http://wiki.eclipse.org/Platform_UI/Bug_Triage_Change_2009"
Comment 4 Eclipse Webmaster CLA 2019-09-06 16:15:47 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.