I think the feature requested here is a bit fuzzy.
[..]
My interpretation of Gerd’s request (from earlier) is that each time the caret moves more than a line (after an edit), the position is added to the stack. But I am not sure if this would be a satisfying heuristic. There should probably be some collapsing of locations based on distance/within the view port.
Gerd: If you do have a clear definition of how it should work, please let me know.
Certainly a fuzzy feature... Back then on small screens it was basically "moved more than a line". Now with large windows, it is trickier to find a good metric. Distance in the view port seems to factor in.
Maybe this would work: still record every change in position that is more than a line, but then when going backward/forward in the history discard positions that are currently visible. Of course this may be too much, so it might need to be more like "visible and not more than y lines away from current cursor position".
And I do think the "jump buffer" should span all files, not be limited to the one currently viewed. So say I work in file x, now go to look at something in file y (or even edit there) and "jump back", it should jump back to file x (even if I closed it!).
And to add extra bells and whistles, there'd be an (optional) visual navigator that shows previous edit locations with context!
Gerd
On 22 Sep 2014, at 18:07, Elia Schito wrote:+1 from here too
I resort for the poor man's version (⌘Z / ⌘⇧Z) all the time, but works only
if there had been an edit of course
Elia
📢 twitter/elia <http://twitter.com/elia>
☕️ github/elia <http://github.com/elia>
On Mon, Sep 22, 2014 at 6:04 PM, Gerd Knops <gerti-textmate@bitart.com>
wrote:
Seconded! A long time ago I used an editor that had this feature (Edison
on Atari ST/TT), that was tremendously useful.
I think I requested that feature several times over the years. If TM
wouldn't be written mostly in C++ (gag) I long since would have added this
and a whole slew of features.
Gerd
On Sep 22, 2014, at 9:09 AM, Matt Neuburg <matt@tidbits.com> wrote:
I have a feature suggestion. I've thought about this for years but it
has only just occurred to me to say something about it.
As you know, I use TextMate to write books. Big books with big chapters.
So it often happens that I edit a chapter, then jump to an earlier / later
bit of that same chapter to make some change entailed by what I was just
writing. Now I want to "go back" to where I was before.
That's the suggestion. TextMate should _automatically_ maintain
"bookmarks" for the location of the two most recent edit locations (places
where I actually typed or deleted text). Thus, I could use the bookmarks
feature to jump back to where I was before.
Just an idea. (A really great idea!) m.
--
matt neuburg, phd = http://www.apeth.net/matt/
pantes anthropoi tou eidenai oregontai phusei
Programming iOS 7! http://shop.oreilly.com/product/0636920031017.do
iOS 7 Fundamentals! http://shop.oreilly.com/product/0636920032465.do
RubyFrontier! http://www.apeth.com/RubyFrontierDocs/default.html
_______________________________________________
textmate mailing list
textmate@lists.macromates.com
http://lists.macromates.com/listinfo/textmate
_______________________________________________
textmate mailing list
textmate@lists.macromates.com
http://lists.macromates.com/listinfo/textmate
_______________________________________________
textmate mailing list
textmate@lists.macromates.com
http://lists.macromates.com/listinfo/textmate
_______________________________________________textmate mailing listtextmate@lists.macromates.comhttp://lists.macromates.com/listinfo/textmate