On Fri, Jul 18, 2008 at 08:49:20AM -0700, Andrew DeFaria wrote:
>If anybody should be inconvenienced here it should be much more the few
>using antiquated equipment than the masses using the equipment of th e
>day - don't you agree?
Last warning: please take your discussion some place other than t
Mark J. Reed wrote:
I think you're missing the point.
Out of the box, on a Linux system, the backspace key works as
intended. Period. You had bogus configuration stuff in your .vimrc,
which is not Linux's fault.
No you're missing the larger point. This is Cygwin - not Linux, though I
know tha
I think you're missing the point.
Out of the box, on a Linux system, the backspace key works as
intended. Period. You had bogus configuration stuff in your .vimrc,
which is not Linux's fault.
So it sounds like you're complaining about the fact that it's possible
to screw up something so fundamen
Mark J. Reed wrote:
It is only in Unix that often the backspace key does not perform the
function > of moving backward a space and deleting the previously
character. I have never, I repeat never had backspace not do a back
space except under Unix - have you?
I've had such issues on many systems
Matt Wozniski wrote:
Well, there's your problem. You told vim that the backspace key sends
0x7F, when in fact it sends 0x08 in your terminal emulator. Vim would
have done the correct thing, if it ever saw a backspace, but it never
saw 0x7F, only 0x08. :fixdel is archaic, and never necessary on m
> It is only in Unix that often the backspace key does not perform the function
> > of moving backward a space and deleting the previously character. I have
> never, I repeat never had backspace not do a back space except under
> Unix - have you?
I've had such issues on many systems. VMS. MVS.
On Thu, Jul 17, 2008 at 12:46 PM, Andrew DeFaria wrote:
> Seems like my problem was I had a set t_kb=^? in my .vimrc as well as the
> aforementioned fixdel. Indeed the mere fact that I included such things in
> my .vimrc indicate that I was having problems with backspace not doing a
> backspace. I
Matt Wozniski wrote:
On Thu, Jul 17, 2008 at 1:45 AM, Andrew DeFaria wrote:
Corinna Vinschen wrote:
WFM, but the behaviour is not identical to Ctrl-D. It doesn't use
the shiftwidth for one thing.
English woman! English!
Respectful.
Huh? Your response make no sense!
Stated differently, on som
On Thu, 17 Jul 2008, Matt Wozniski wrote:
Not very hard if you take the time to learn a bit about terminals.
on a UNIX keyboard either sends ^? or ^H. If you have "set
backspace=indent,eol,start" (or, equivalently, "set backspace=2") in
your ~/.vimrc, vim will correctly delete over automati
On Thu, Jul 17, 2008 at 1:45 AM, Andrew DeFaria wrote:
> Corinna Vinschen wrote:
>> WFM, but the behaviour is not identical to Ctrl-D. It doesn't use the
>> shiftwidth for one thing.
>
> English woman! English!
Respectful.
> Stated differently, on some versions of vim on some OSes, after hitting
Corinna Vinschen wrote:
On Jul 16 08:50, Andrew DeFaria wrote:
Robert Latest wrote:
Thanks folks, I didn't know about Ctrl-D. Of course that's all I'm
gonna use now, because it is so Vim. One thing that I don't
understand is that indents eight spaces whereas Ctrl-D
un-indents only four. I'll
Put it another way: in vim (in insert mode), the tab key just inserts
a tab (which it displays as the number of spaces needed to get to the
next even value of whatever tabstop is set to). It has nothing to do
with vim's idea of indentation, automatic or otherwise.
The control-D ("outdent" or "uni
Robert Latest wrote:
>
> Thanks folks, I didn't know about Ctrl-D. Of course that's all I'm
> gonna use now, because it is so Vim. One thing that I don't understand
> is that indents eight spaces whereas Ctrl-D un-indents only
> four. I'll check on that. Actually I've got ":set sw=4" in my vimrc,
On Jul 16 08:50, Andrew DeFaria wrote:
> Robert Latest wrote:
>> Thanks folks, I didn't know about Ctrl-D. Of course that's all I'm gonna
>> use now, because it is so Vim. One thing that I don't understand is that
>> indents eight spaces whereas Ctrl-D un-indents only four. I'll check
>> on tha
Robert Latest wrote:
Thanks folks, I didn't know about Ctrl-D. Of course that's all I'm
gonna use now, because it is so Vim. One thing that I don't understand
is that indents eight spaces whereas Ctrl-D un-indents only
four. I'll check on that. Actually I've got ":set sw=4" in my vimrc,
maybe
On Jul 16 11:49, Robert Latest wrote:
> Thanks folks, I didn't know about Ctrl-D. Of course that's all I'm
> gonna use now, because it is so Vim. One thing that I don't understand
> is that indents eight spaces whereas Ctrl-D un-indents only
> four. I'll check on that. Actually I've got ":set sw=4
Thanks folks, I didn't know about Ctrl-D. Of course that's all I'm
gonna use now, because it is so Vim. One thing that I don't understand
is that indents eight spaces whereas Ctrl-D un-indents only
four. I'll check on that. Actually I've got ":set sw=4" in my vimrc,
maybe that has to do with it.
On Fri, Jul 11, 2008 at 9:01 AM, Corinna Vinschen wrote:
> On Jul 11 14:53, Robert Latest wrote:
>> Hello list,
>>
>> When writing stuff in "vim", I can't unindent without first havin to
>> leave the Insert mode. In other words, I type a line, hit "enter",
>> then "tab", and do the next line. When
On Jul 11 14:53, Robert Latest wrote:
> Hello list,
>
> When writing stuff in "vim", I can't unindent without first havin to
> leave the Insert mode. In other words, I type a line, hit "enter",
> then "tab", and do the next line. When I hit enter again, the cursor
> goes onto the first position of
19 matches
Mail list logo
