On 3/27/06 at 9:17 AM,  Patrick Woolsey <[EMAIL PROTECTED]> wrote:

> Gregory Ramsperger <[EMAIL PROTECTED]> sez:
> 
> >On to my question. Is there any way to extend BBEdit's built-in emacs
> >key bindings? I like the fact that they are really more key sequences
> >than bindings. I have become accustomed to using things like "C-c p e"
> >to open a file for editing Perforce. I know I can map this to something
> >with "Set Menu Keys" but I am running out of convenient combiniations.
> >It is nice to just know that "C-c p" starts the Perforce commands and
> >then run the sub-commands (like e for edit).
> >
> 
> The short answer is no, because those multi-key sequences require special
> treatment and are currently hard-wired.
> 
> Are you looking for a complete layer of Emacs-like behavior, or instead do
> you just want to add some specific additional mappings?
> 

Hi Patrick-

I wouldn't mind a full Emacs-like implementation, but what I specifically like 
is the command-subcommand series.

I prefer to use the keyboard for common commands, but I have some pretty 
awkward commands mapped to things that are "secondary." My most frequently used 
items fill up the easy to hit key sets. In Emacs, these are extended to a 
second layer rather than hitting a slew of characters at once.

It doesn't need to follow Emacs exactly, I mostly just noted that there was 
some foundation for this existing in BBEdit. A "command map" of sorts that the 
user could define and drill into would probably suffice.

---

Perhaps someone could create an open-source plugin based on the GNU Emacs code. 
Commands could be implemented in elisp. While you're at it, elisp-based 
language modules would be nice to....

-Gregory

--
------------------------------------------------------------------
Have a feature request? Not sure the software's working correctly?
If so, please send mail to <[EMAIL PROTECTED]>, not to the list.
List FAQ: <http://www.barebones.com/support/lists/bbedit_talk.shtml>
List archives: <http://www.listsearch.com/BBEditTalk.lasso>
To unsubscribe, send mail to:  <[EMAIL PROTECTED]>

Reply via email to