On Thu, Jan 23, 2003 at 11:48:07AM -0800, Michael Barrett wrote:
> That did it. Any idea why that would be needed for mutt but not for regular
> vi?
not exactly. terminal handling is quite complicate. i found some
hints in the vim-user-doc. it has something to do which ASCII
code is generated whe
That did it. Any idea why that would be needed for mutt but not for regular
vi?
Thanks a ton for your help. Wow, it's so nice to be able to use the backspace
when I typo. :)
On Thu, Jan 23, 2003 at 03:02:27PM +0100, Toni Schmidbauer wrote:
> On Thu, Jan 23, 2003 at 12:16:00AM -0800, Michael Bar
# [EMAIL PROTECTED] / 2003-01-23 07:48:24 -0800:
> On Thu, Jan 23, 2003 at 12:26:53PM +0100, Roman Neuhauser wrote:
>
> > I had this problem some time ago: rxvt (or was it vim?) started from
> > my window manager's menu (which was then blackbox) behaved properly,
> > while if started t
On Thu, Jan 23, 2003 at 12:26:53PM +0100, Roman Neuhauser wrote:
> I had this problem some time ago: rxvt (or was it vim?) started from
> my window manager's menu (which was then blackbox) behaved properly,
> while if started through bbkeys (an app that handles keyboard
> shortcuts
On Thu, Jan 23, 2003 at 12:16:00AM -0800, Michael Barrett wrote:
> Anyways, when I run vim from the command line, if I'm in insert mode and I
> hit the backspace key it acts normally. IE: It erases the character to the
> left of the cursor.
try these two options in your .vimrc
set t_
# [EMAIL PROTECTED] / 2003-01-23 00:16:00 -0800:
> FreeBSD 4.7
> Mutt 1.4i (2002-05-29)
> Vim 6.1.271
>
> Anyways, when I run vim from the command line, if I'm in insert mode and I
> hit the backspace key it acts normally. IE: It erases the character to the
> left of the c
