Re: Feature or bug? dw oddities

Elmar Hinz writes: > Summarising this, you think vim is behaving differently than most > other vi derivates? > > Why is the comment quoted by Christian Brabandt telling, vim tries to > behave like vi? "vi derivates" is a bit misleading term. All of the programs I

Re: Feature or bug? dw oddities

On 2016-02-04, Christian Brabandt wrote: > I think, it is this part of the code from op_delete() > > /* >* Imitate the strange Vi behaviour: If the delete spans more than one >* line and motion_type == MCHAR and the result is a blank line, make > the >

Re: Feature or bug? dw oddities

Elmar Hinz writes: > Hello, > > I am working on a Python clone of vim, which requires to inspect Vim > behaviour in detail. Some behaviour looks odd and I like to know if it > is a bug or what is the reasoning of that behaviour. This is my first > observation: > > Given,

Re: Can you edit EBCDIC files on non-OS390 builds of VIM?

Justin Dearing writes: > I'd like to edit EBCDIC encoded files in VIM on windows vim Windows VIM apparently supports all windows codepages as file encodings [++enc=cpNNN] including cp37 and cp1047, etc. It seems to work fine for me, though I'm not sure if there are any

Re: editing a _corrupted_ CP1252 file

Erik Christiansen writes: > Ah, not simply remapping, then. For UTF-8, Vim has the "8g8" command, to > hop to the next encoding violation. Unfortunately, there's no mention > there of any ability to do that for CP1252. Works for me if the file has been opened with

Re: problem: editing a _corrupted_ CP1252 file

Kenneth Reid Beesley writes: > I have a little alias gvim1252 set to > > gvim -c “e ++enc=cp1252” you'll want to add ++bad=keep to that; it should do mostly what you asked for below with the <81> and such. It'll open the file in read-only mode, and won't let you

Re: Unintentionally closing Vim with many buffers open

On 2015-12-05, wolfv wrote: > Sometimes I unintentionally close Vim with many buffers open. > Then I have to reopen Vim and reopen all the buffers I was working on. > Is there a way to prevent this, like a plugin that prompts "Multiple > buffers are open, are you sure you

Re: "+y in vim put all stuff to "* not to "+

On 2015-11-25, Roman wrote: > Why vnoremap "+y in vim visual mode puts all stuff to "* not to "+ > But "+y in vim working fine. In gvim all working fine. As I understand it, only x11 gvim makes a distinction between "* and "+. In win32, these both refer to the clipboard. In

Re: Go to Japanese character

On 2015-11-23, bob beckett wrote: > Thank you for your suggestion. Unfortunately, it finds all non-ASCII > characters in the entire file, and it does not move the cursor to the first > Japanese (i.e. non-ASCII) character in the current line. And does what with them,

Re: Question about language specific mappings

On 2015-11-20, Dmitri Vereshchagin wrote: > * Tony Mechelynck [2015-11-20 23:54]: >> N°№ U+2116 NUMERO SIGN > > Thank you. It is very clever. I suppose you use AZERTY keyboard > layout. I have ЙЦУКЕН (JCUKEN) keyboard and

Re: vim: register * and + missing in ubuntu1404 server

John Little writes: > Maybe you're thinking of gpm mouse support. Install the package gpm, > and with set mouse=a in your .vimrc, a middle click does a paste, but > from the unnamed register; you still don't get a separate "* and "+ > AFAICS. Why not? gpm has a

Re: [Resolved]: Console vim beeps with file beeper.txt

"'Suresh Govindachar' via vim_use" writes: > Additional background info: I am on Windows 7 64 bit, running console > Vim inside ConEmu. > > Thanks for the replies. Indeed it was bullets at the beginning of > each line. Opening the file in gvim shows the bullets. What

Re: Problem using vim in csh on linux

Tim Chase writes: > And if your screen/$TERM gets corrupted, there's always ed(1) ;-) Or ex, which is technically "vi by another name" but almost certainly not what he wants. To add to the list of suggestions - if they are different, see what the output of :set termcap

Re: system command takes a different environment variable from current shell?

"Karl (Xiangrong) Cai" writes: > I thought this was pretty clear :-): And here are the steps again: > > 1) xterm with a login tcsh shell is created. At this time $c is set to > /volume/current. > 2) do " setenv c /volumeNew/current". As this time "echo $c" in this > shell shows

Re: "fictious" not recognized as spelling error

Tim Chase writes: > On 2015-10-19 09:52, Paul wrote: >> For a reason that I haven't been able to suss out, "fictious" not >> recognized as spelling error. > > Not sure what OS you're on or what system dictionary you're using, > but that word/spelling is present in my > >

Re: system command takes a different environment variable from current shell?

"Karl (Xiangrong) Cai" writes: > Regarding " What is your _exact_ set of steps that results in echo $c > showing /volumeNEW/current" > > 641% echo $c > /volume/current > 642% setenv c /volumeNew/current > 643% echo $c > /volumeNew/current Which shell is this? The original one,

Re: system command takes a different environment variable from current shell?

"Karl (Xiangrong) Cai" writes: > And in vim, when I do 1) echo $c, and 2) let x = system(“echo $c”); > and then “echo x”, both shows “/volume/current”, which is expected; > Then inside this shell I set this variable to another value: > <<< > 603% setenv c /volumeNEW/current >

Re: Where does gvim look for fonts in cygwin x-windows

> Paul gmail.com> writes: >> I'm finding that cygwin's gvim no longer seems to use the same cryptic >> font names as xfontsel. They are much simpler names. So it seems >> that gvim doesn't use the X-window fonts. I'm at a loss for how to >> select cygwin packages that will expand my font