[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-bugs-dist
Subject:    [kdevelop] [Bug 140905] open just link -- do not smart-follow it
From:       Denis Kaznadzey <dkaznadzey () yahoo ! com>
Date:       2013-04-26 6:31:31
Message-ID: bug-140905-17878-IeID8LSkxQ () http ! bugs ! kde ! org/
[Download RAW message or body]

https://bugs.kde.org/show_bug.cgi?id=140905

Denis Kaznadzey <dkaznadzey@yahoo.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |dkaznadzey@yahoo.com

--- Comment #13 from Denis Kaznadzey <dkaznadzey@yahoo.com> ---
Dear KDevelop developers,
Please reconsider this issue.
When some of the directories that lead to the file being edited are symlinked,
smart-opening creates a lot of confusion and inconvenience. There are good
reasons to symlink directories: for instance, the entire project may be located
in symlinked directory so that switching the symlink would allow changing the
particular version of code (or type of build) being worked on. After switching
the symlink, I would expect that KDevelop session points to the projects in
symlinked directories. However, the projects in the KDevelop sessions are bound
to fully resolved locations, so switching symlink does not do the job. 

And please revisit the argument that the tool should better not try to outsmart
the user, who definitely has reasons for symlinks if he uses them. You may add
visual indication that two or more open files actually refer to same physical
file (for instance, display 'link count' near the file name in the project
window if the file is open under a number of names; also the editor title tab
may display the link count and a tooltip listing all names under which this
file is open). This would allow to have a number of different names in the list
of open files that refer to same actual file, and have all of them refer to one
editor window.

(To make this more convincing, let's imagine that hardlinks are used instead of
symlinks. How the editor would handle such case?)

-- 
You are receiving this mail because:
You are watching all bug changes.
[prev in list] [next in list] [prev in thread] [next in thread]