Re: How to map the # key to a command?

2023-05-13 Thread Paul Fox
chris wrote: > In the end I have used E as I never use[d] the default binding for > that. So:- > > bind-key edit-file E > > Does just what I want, gives me a single key way to edit files loaded > as a result of 'vi ' which I have just created a need for. > I might even use lower case

Re: How to map the # key to a command?

2023-05-13 Thread Chris Green
On Sat, May 13, 2023 at 07:48:25AM -0400, Paul Fox wrote: > chris wrote: > > On Sat, May 13, 2023 at 11:09:59AM +0100, Chris Green wrote: > > > On Sat, May 13, 2023 at 11:04:26AM +0100, Chris Green wrote: > > > > I can map the # key to do ^Xe 'manually' when running vile simply by > > > >

Re: How to map the # key to a command?

2023-05-13 Thread Paul Fox
chris wrote: > On Sat, May 13, 2023 at 11:09:59AM +0100, Chris Green wrote: > > On Sat, May 13, 2023 at 11:04:26AM +0100, Chris Green wrote: > > > I can map the # key to do ^Xe 'manually' when running vile simply by > > > going to the colon prompt and entering 'map ', then entering # in > > >

Re: How to map the # key to a command?

2023-05-13 Thread Chris Green
On Sat, May 13, 2023 at 11:09:59AM +0100, Chris Green wrote: > On Sat, May 13, 2023 at 11:04:26AM +0100, Chris Green wrote: > > I can map the # key to do ^Xe 'manually' when running vile simply by > > going to the colon prompt and entering 'map ', then entering # in > > response to 'change this

Re: How to map the # key to a command?

2023-05-13 Thread Chris Green
On Sat, May 13, 2023 at 11:04:26AM +0100, Chris Green wrote: > I can map the # key to do ^Xe 'manually' when running vile simply by > going to the colon prompt and entering 'map ', then entering # in > response to 'change this string' and, finally ^Xe in response to 'to > this new string'. The #