vim: thesaurus

2016-02-12 Thread Guido Milanese
Dear Experts, I am using gvim (on xubuntu 15.10) for most of my daily work. I write my scholarly work using LaTeX + BibTeX, and I normally use the excellent LaTeX plugin. I recently tried TeXStudio, and the only feature I found better was the easy access to the [Libre | Open]office thesaurus. I

Why isn't replaced text registered?

2016-02-12 Thread 'Elmar Hinz' via vim_use
Hello, the r and R commands count to insertions and deletions. Contrary to the other commands of this group the deleted text isn't stored into a register. I can image, that the historical reason is to be found on the level of implementation, because replacement spans over multiple inputs. Is

Re: Feature or bug? Funny behaviour of cw on whitespace.

2016-02-12 Thread 'Elmar Hinz' via vim_use
> It doesn't say why though, and the reason IIUC is that vi did it that way, > and it's such a basic command that millions are used to it. IMO we'd be > better off with consistency, c{motion} is like d{motion} then enter insert > mode, without this special case, but after 40 years... > >

Re: Feature or bug? Funny behaviour of cw on whitespace.

2016-02-12 Thread John Little
On Friday, February 12, 2016 at 1:53:00 AM UTC+13, Erik Christiansen wrote: > But ":h cw" opens with a defence of this "Special case: ...change-word". It doesn't say why though, and the reason IIUC is that vi did it that way, and it's such a basic command that millions are used to it. IMO we'd

Repetition related questions

2016-02-12 Thread 'Elmar Hinz' via vim_use
Hello all, I bundle some questions related to repetition. 1.) I can repeat the operation by the .-command, one of the most brilliant features of vim. Is there a command to repeat the last movement or even the last movement-operation-pair? 2.) To enable the repetition of t, T, f, F by "," and

Re: vim: thesaurus

2016-02-12 Thread Russell Urquhart
Hi Guido, I too use vim for my technical writing. AFAIK, i think the online thesaurus is the only thing available. (I hope we find out that there are other options.) You might also want check out the Grammer checker plugin for vim: http://www.vim.org/scripts/script.php?script_id=3223 If you

Re: vim: thesaurus

2016-02-12 Thread Nicola
On 2016-02-12 09:44:05 +, Guido Milanese said: Dear Experts, I am using gvim (on xubuntu 15.10) for most of my daily work. I write my scholarly work using LaTeX + BibTeX, and I normally use the excellent LaTeX plugin. I recently tried TeXStudio, and the only feature I found better was the

Re: vim: thesaurus

2016-02-12 Thread Nicola
On 2016-02-12 14:16:50 +, Nicola said: Another possibility is to download an .oxt file, change the suffix to .zip, uncompress it, and open the thesaurus .dat file (it is a text file). I have taken a quick look at one of them, and it should not be too hard to turn it into a format usable by

Re: vim: thesaurus

2016-02-12 Thread Nicola
On 2016-02-12 18:04:09 +, Nicola said: On 2016-02-12 14:16:50 +, Nicola said: Another possibility is to download an .oxt file, change the suffix to .zip, uncompress it, and open the thesaurus .dat file (it is a text file). I have taken a quick look at one of them, and it should not be

Re: vim: thesaurus

2016-02-12 Thread David Woodfall
Dear Experts, I am using gvim (on xubuntu 15.10) for most of my daily work. I write my scholarly work using LaTeX + BibTeX, and I normally use the excellent LaTeX plugin. I recently tried TeXStudio, and the only feature I found better was the easy access to the [Libre | Open]office thesaurus. I

Re: Feature or bug? Funny behaviour of cw on whitespace.

2016-02-12 Thread 'Elmar Hinz' via vim_use
> As pointed out once or twice upthread, please read ":h cw", in particular > the last paragraph. For those who can see, it is there. > > Erik Shouldn't an editor startup with the most consistent settings by default? Elmar -- -- You received this message from the "vim_use" maillist. Do not

Re: Feature or bug? Funny behaviour of cw on whitespace.

2016-02-12 Thread Erik Christiansen
On 12.02.16 03:02, Elmar Hinz wrote: > > > It doesn't say why though, and the reason IIUC is that vi did it > > that way, and it's such a basic command that millions are used to > > it. IMO we'd be better off with consistency, c{motion} is like > > d{motion} then enter insert mode, without this