Do Bookmarks not persist between sessions? I just spent an hour setting up bookmarks in a markdown syntax template, thinking I'd be able to open the document in the future and F2 (Next Bookmark) through the doc to make changes.
It seems bookmarks are not permanent. Why not? Is there plans to make them so?
-t
On 27.01.2005, at 03:53, Tim Martens wrote:
Do Bookmarks not persist between sessions? I just spent an hour setting up bookmarks in a markdown syntax template, thinking I'd be able to open the document in the future and F2 (Next Bookmark) through the doc to make changes.
It seems bookmarks are not permanent. Why not? Is there plans to make them so?
Hmm, where would you like the info to be stored? Inside the file, using some special syntax that's alien to other editors and compilers? Or in a different location, which would mean the bookmark data could be corrupted by editing the file in a different editor. This issue is clearly not as simple as it sounds, because TM works on plain text files, in contrast to a custom file format.
IMO, bookmarks cannot be implemented properly (go ahead Allan, prove me wrong :-). Automatic bookmarks (that "boomark" each line matching a certain pattern), would be much more useful.
That way, I could still bookmark arbitrary lines by including the pattern in a comment, for example. It's not so differen from using special syntax to store the information inside the file, but then I get to decide on how to embed it, depending on what I use the file for.
HTH, -Ralph.
On 27.01.2005, at 12:29, Brian Lalor wrote:
On Jan 27, 2005, at 6:19 AM, Ralph Pöllath wrote:
Hmm, where would you like the info to be stored?
How about in the project file?
Not a bad idea for files that actually belong to a project. But still, how do you store the inormation? Just the line numbers? Then what happens if I add a lline with a different editor? To do it right, you would have to keep a copy of the file and merge it with the edited file (like cvs or svn do) just to restore the bookmarks information. And even that isn't guaranteed to work.
I admit, persistent bookmarks might be nice for people who use TM exclusively.
Cheers, -Ralph.
On Jan 27, 2005, at 1:41 AM, Ralph Pöllath wrote:
How about in the project file?
Thatst what I'd imagine.
Not a bad idea for files that actually belong to a project. But still, how do you store the inormation? Just the line numbers? Then what happens if I add a lline with a different editor?
I could care less about other editors. We're all TM users here and having a TM only feature cold bring more interest to those considering moving to TM.
On Jan 27, 2005, at 12:19, Ralph Pöllath wrote:
IMO, bookmarks cannot be implemented properly (go ahead Allan, prove me wrong :-). Automatic bookmarks (that "boomark" each line matching a certain pattern), would be much more useful.
Yes, automatic bookmarks are on the to-do. And you're right about the meta-data problem. I want to keep as much as possible automatic, because meta-data is easily lost and/or the file can get out-of-synch.
With my own use of bookmarks I do also appreciate that these are reset on a new session -- but when/if I introduce a general system for meta-data (or the OS does) bookmarks are likely to be optionally kept there.
On 27/01/2005, at 10:19 PM, Ralph Pöllath wrote:
IMO, bookmarks cannot be implemented properly (go ahead Allan, prove me wrong :-). Automatic bookmarks (that "boomark" each line matching a certain pattern), would be much more useful.
It's a common misconception that if there are significant situations in which some idea won't work, it's "impossible". Often, though, having something work most of the time is still better than not having it at all.
* Store bookmarks in the project as line number, and some of the context surrounding the bookmark. * If, on loading the file, the number and context don't match, start looking up and down for the first line that matches the saved context to a certain degree of tolerance. * If some bookmarks are still unaccounted for, delete them and pop up a dialog saying "This file was modified since it was last opened in [[Project Name]]. Some of your bookmarks have been removed."
Under certain circumstances this would lead to bookmarks being lost (or even moved), but it would work well enough for 90% of cases.
Charles Miller
On Jan 27, 2005, at 7:31 PM, Charles Miller wrote:
It's a common misconception that if there are significant situations in which some idea won't work, it's "impossible". Often, though, having something work most of the time is still better than not having it at all.
- Store bookmarks in the project as line number, and some of the
context surrounding the bookmark.
- If, on loading the file, the number and context don't match, start
looking up and down for the first line that matches the saved context to a certain degree of tolerance.
- If some bookmarks are still unaccounted for, delete them and pop up
a dialog saying "This file was modified since it was last opened in [[Project Name]]. Some of your bookmarks have been removed."
Under certain circumstances this would lead to bookmarks being lost (or even moved), but it would work well enough for 90% of cases.
Bravo Charles!
On 28.01.2005, at 06:31, Charles Miller wrote:
On 27/01/2005, at 10:19 PM, Ralph Pöllath wrote:
IMO, bookmarks cannot be implemented properly (go ahead Allan, prove me wrong :-). Automatic bookmarks (that "boomark" each line matching a certain pattern), would be much more useful.
It's a common misconception that if there are significant situations in which some idea won't work, it's "impossible". Often, though, having something work most of the time is still better than not having it at all.
- Store bookmarks in the project as line number, and some of the
context surrounding the bookmark.
- If, on loading the file, the number and context don't match, start
looking up and down for the first line that matches the saved context to a certain degree of tolerance.
- If some bookmarks are still unaccounted for, delete them and pop up
a dialog saying "This file was modified since it was last opened in [[Project Name]]. Some of your bookmarks have been removed."
Yup, that's what I referred to as "merging".
Under certain circumstances this would lead to bookmarks being lost (or even moved), but it would work well enough for 90% of cases.
I guess it boils down to a matter of taste. I don't deny that all of this would be helpful for some or even most people, but personally, I wouldn't use e.g. a filesystem that let's me get at my data only 90% percent of the time. Sometimes, and for some people, it's those 10% that count.
Additionally, you and I know why that system wouldn't work in some small percentage of cases. But what about those who don't know or care about the implementation?
I could be wrong, but I assume that TM is mainly used by power users, and I further assume that those tend to work with structured text (like code, xml, etc) - that's why we have all these bundles. So IMO, it would make a lot more sense to exploit the text's inherent structure for navigation. It works 100% percent of the time even for non-project files, doesn't require storing extra data, and rewards you for structuring your text :-)
Cheers, -Ralph.
On 28. jan 2005, at 10:36, Ralph Pöllath wrote:
On 28.01.2005, at 06:31, Charles Miller wrote:
On 27/01/2005, at 10:19 PM, Ralph Pöllath wrote: Under certain circumstances this would lead to bookmarks being lost (or even moved), but it would work well enough for 90% of cases.
I guess it boils down to a matter of taste. I don't deny that all of this would be helpful for some or even most people, but personally, I wouldn't use e.g. a filesystem that let's me get at my data only 90% percent of the time. Sometimes, and for some people, it's those 10% that count.
Yeah but those people can then not use the system. No reason that all the other people can't :-p. I like the "merging" idea, as it was called. Quite similar to the way patch resolves discrepancies.
Additionally, you and I know why that system wouldn't work in some small percentage of cases. But what about those who don't know or care about the implementation?
It's a simple matter of adding to the help file that bookmarks can not be expected to be preserved 100% if the file is modified outside of TextMate. This is nothing new... computers aren't magic.
I could be wrong, but I assume that TM is mainly used by power users
..which is exactly why the above won't be a problem, IMO.
-
Allan Odgaard -
Brian Lalor -
Charles Miller -
Ralph Pöllath -
Sune Foldager -
Tim Martens -
Tim Martens