Just want to throw this out there: (1) place bookmark in file at the signature of a Ruby method (2) comment out the whole method displaces the bookmark so that it now moves itself to be after the commented out code? Seems strange to me. Feature or bug? I love bookmarks though : )
-- Best regards, Lang Riley
On Mar 8, 2005, at 20:49, Lang Riley wrote:
Unfortunately when running a transformation (like a command) on the selection, there isn't any easy way for me to keep the location of meta-data (like bookmarks).
I guess I could look into some heuristics, like when the number of lines are the same, it should re-use line numbers etc. -- but it's unfortunately not that simple to implement, and it'll always be very easy to break whatever I come up with...
On 09.03.2005, at 11:14, Allan Odgaard wrote:
Just thinking out loud..
Maybe you could store the actual information as a special character attribute (an invisible style, if you like) and just display a bookmark symbol in every line that contains such characters.
What are the semantics of a bookmark? Does a bookmark mark a line number? Or the actual content of a line?
As I mentioned before, I think that automatic bookmarks (based on language-specific regex) are way superior to custom bookmarks: Their behaviour is well-defined, and they can be calculated on the fly (no need to store file metadata).
Cheers, -Ralph.
On Mar 9, 2005, at 12:52, Ralph Pöllath wrote:
Generally the text goes through an external command, so I can't keep character attributes -- I can however use unicode replacement (object) characters for meta-data, but not all commands would like this.
That really depends on the purpose of bookmarks. For me, I have at most 3-4 bookmarks in my source code, and that are the hot spots I work on -- so I use a bookmark if I want to leave the current function but have a way to quickly return, or jump back and forth between two places in my source.
Auto-generated bookmarks based on regex really sounds like a rather different functionality (this is more like the requested function popup) -- for this purpose I'm introducing a way to query the source code using an xpath-inspired system (with source structure provided by the syntax files), which will make the way for function popups and more (e.g. also list of included files, variables in current class etc., all defined as queries -- but this is currently something I experiment with and not set in stone).