Hi Allan,
Sometimes I find myself in the situation where I try a key combination which doesn't do what I thought but moves the carat leaving me uncertain what action I have just performed. I know I can hit undo but given the non-atomic undo nature it leaves me with doubts about whether my file is changed.
Would it be possible to add a feature that tells you what function a key combination will invoke?
What I have in mind would be:
select "identity key" press key combination, e.g. Cmd+Opt+V TxMt pops up a dialog identifying the bundle & command this will activate Choose "yes" Executes command Choose "no" Does nothing
This would help me, (a) because I could work out what I *did* do, and (b) because I could help myself learn key combos safely (by either passing through to the action or not).
Just a thought, not sure how good of a one though ;-)
M
-- Matt Mower :: http://matt.blogs.it/
On 07/11/2005, at 10.05, Matt Mower wrote:
[...] I can hit undo but given the non-atomic undo nature it leaves me with doubts about whether my file is changed.
Undo will undo exactly the action you did, nothing more, nothing less. So if you have a column selection and fire an action that overwrites it, run a command, and insert a snippet, pressing undo will bring you back to before that, and even with the column re- selected (something I haven't seen other editors do).
Would it be possible to add a feature that tells you what function a key combination will invoke?
This is on the to-do -- one problem though is that a) I'm not really aware of all actions executed (although what the framework does w/o me knowing is minimal), and b) I can't fully mimic how the system translate menu keys. This is not just the Dvorak - Qwerty hybrid, but things like option-cmd 8, which on the US keyboard would fire an action bound to option-cmd 8, but on a “most of Europe” keymap, would fire an action bound to cmd [.
Althoigh I think by now, I'm pretty close to mimicking the system with my rather heuristic approach…
On Nov 7, 2005, at 4:25 AM, Allan Odgaard wrote:
Undo will undo exactly the action you did, nothing more, nothing less.
This of course does not include cursor navigation, which cannot be undone. I am guessing this is the standard and expected behavior for a bunch of very obvious reasons, but I find myself quite often in the situation where I've pressed Cmd-downarrow thinking it would take me one paragraph or half a page down, and suddenly find myself at the end of the document with no direct way of going back to where I was. Is there a, possibly separate undo command, that takes you back along cursor navigation steps? I would personally like that if it is not too hard to code.
Haris
On 07/11/2005, at 14.33, Charilaos Skiadas wrote:
[...] I find myself quite often in the situation where I've pressed Cmd-downarrow thinking it would take me one paragraph or half a page down, and suddenly find myself at the end of the document with no direct way of going back to where I was.
Often undo + redo will bring you back, granted you had done some edit operation at your previous location.
Gerd suggested keeping edit locations on a stack and allowing to go back to these -- but this is a little out in the future.
Hi Allan,
Thanks the reply.
On 07/11/05, Allan Odgaard throw-away-1@macromates.com wrote:
On 07/11/2005, at 10.05, Matt Mower wrote:
[...] I can hit undo but given the non-atomic undo nature it leaves me with doubts about whether my file is changed.
Undo will undo exactly the action you did, nothing more, nothing less.
I should have a little more confidence.
As another suggestion (which is probably already in your list) would it be possible for the Undo menu action to describe the last action taken (e.g. I can see "Undo Typing" in the Edit menu right now).
This is on the to-do -- one problem though is that a) I'm not really aware of all actions executed (although what the framework does w/o me knowing is minimal), and b) I can't fully mimic how the system
I'm surprised you can't be aware of all actions executed -- seems like that would be a somewhat precarious position for an app to be in. Would that prevent you from also reflecting the action to be undone in the Edit menu?
Regards,
Matt -- Matt Mower :: http://matt.blogs.it/
On 07/11/2005, at 14.36, Matt Mower wrote:
As another suggestion (which is probably already in your list) would it be possible for the Undo menu action to describe the last action taken (e.g. I can see "Undo Typing" in the Edit menu right now).
This is rather difficult for me to administrate, so chances are low.
[...] I'm surprised you can't be aware of all actions executed -- seems like that would be a somewhat precarious position for an app to be in.
This is what gives you consistency across applications, allow applications to be accessed by disabled users, cause OS upgrades to introduce new features in existing applications, and so on -- you want as much as possible to be handled by the OS/framework.
TM though is a little atypical, in that I overwrite a lot of standard behavior (not always ideal, withnessed e.g. by the broken CJK input method), but there are still much which is handled by the framework, and e.g. when you press cmd-C, TextMate does not see this key, it sees the “copy:” action method (and doesn't know it was a key press that resulted in the message).
On 11/7/05, Matt Mower matt.mower@gmail.com wrote:
As another suggestion (which is probably already in your list) would it be possible for the Undo menu action to describe the last action taken (e.g. I can see "Undo Typing" in the Edit menu right now).
Yet another idea: an optional emacs-style status display that echoes the name of the most recent command. I have no idea how hard or easy this would be to implement, but from a user interface point of view it's a well-established solution to the "what did I just do?" problem.
pb
p.s. This is my first post to the list -- I'm a recent happy convert to TextMate.
-- paul bissex 69.55.225.29 01061-0847 72°39'71"W 42°19'42"N
-
Allan Odgaard -
Charilaos Skiadas -
Matt Mower -
Paul Bissex