On Di, 14 Apr 2020, Brian L. Matthews wrote:
> While this is more software design philosophy than vim-specific, it's
> because every configurable behavior requires code to parse the new option
> (however minimal), code to use the new option, one or more tests,
> documentation changes, it makes t
Yes, I hadn't noticed it, but John Horton Conway died a few days ago.
To load the "game of life" mappings once Vim is up,
:runtime macros/life/life.vim
then (in Normal mode) either g (go); or I (uppercase i for initialize)
followed by either C (compute one step) or R (run). After I you can
edi
Many years ago I wrote Conway's Game of Life in vi macros.
Not vimscript, macros. I posted them, uuencoded, to comp.editors
where you might still find them with Google Groups searches.
But Bram Moolenaar liked the effort, so you can still find those
macros easily. On my Ubuntu system, they are in
On Tue, Apr 14, 2020 at 01:44:50PM -0700, Brian L. Matthews wrote:
> > You don't need CTRL-W at all if you don't mind hitting more keys, but
> > since we do have it and configurable behaviour, why not cover all the
> > variations people could want?
>
> While this is more software design philosophy
On 4/14/20 11:45 AM, Tavis Ormandy wrote:
On Tue, Apr 14, 2020 at 11:34:28AM -0700, Brian L. Matthews wrote:
Yeah, would need another value in 'backspace'. CTRL-W stopping at the
insert point has always been the behavior.
:set backspace=indent,eol,start,nostop
Can't think of a good name
Hello:
I can use a balloon expression (onlookers: see :help 'bexpr') that
creates a small balloon text -- but it persists when I change workspaces
(Scientific Linux and I also use mate: yum -y groupinstall mate-desktop)
(ie. ctrl-alt-arrow). When its displayed on the wrong workspace, its
ann
On Tue, Apr 14, 2020 at 11:34:28AM -0700, Brian L. Matthews wrote:
> > Yeah, would need another value in 'backspace'. CTRL-W stopping at the
> > insert point has always been the behavior.
> > :set backspace=indent,eol,start,nostop
> > Can't think of a good name for "nostop", could be improved.
On 4/14/20 11:23 AM, Bram Moolenaar wrote:
Christian wrote:
On Di, 14 Apr 2020, Tavis Ormandy wrote:
To be clear, very detailed reproduction steps:
1. In a new file, write this:
one two three
2. Enter normal mode, position the cursor after "two" and enter insert
mode, then type "four".
Christian wrote:
> On Di, 14 Apr 2020, Tavis Ormandy wrote:
>
> > To be clear, very detailed reproduction steps:
> >
> > 1. In a new file, write this:
> >
> > one two three
> >
> > 2. Enter normal mode, position the cursor after "two" and enter insert
> >mode, then type "four". It should
Hello:
I use balloons -- (see :he bexpr) -- but they persist when I change
workspaces using ctrl-alt-arrow (workspaces are done via Mate, yum -y
groupinstall mate-desktop ).
Having a balloon in an unrelated workspace is incorrect. I suppose I
could use FocusLost and force the issue, but it s
On Di, 14 Apr 2020, Peng Yu wrote:
> Could you show the complete command? I can not get it work. Thanks.
Seems not to be easily possible.
Best,
Christian
--
Wie man sein Kind nicht nennen sollte:
Bernhard Diener
--
--
You received this message from the "vim_use" maillist.
Do not top-po
On Di, 14 Apr 2020, Tavis Ormandy wrote:
> To be clear, very detailed reproduction steps:
>
> 1. In a new file, write this:
>
> one two three
>
> 2. Enter normal mode, position the cursor after "two" and enter insert
>mode, then type "four". It should look like this:
>
> one twofour thre
Could you show the complete command? I can not get it work. Thanks.
On 4/14/20, Christian Brabandt wrote:
>
> On Di, 14 Apr 2020, Peng Yu wrote:
>
>> I still get something printed. How to turn it off? So `< /dev/tty` is
>> not needed anymore for both cases?
>
> Use the :silent modifier?
>
> Best
On Tue, Apr 14, 2020 at 06:56:32PM +0200, Christian Brabandt wrote:
> > Thanks, but I'm not in compatible mode. In compatible mode, AFAICT, CTRL-W
> > does not remove at all and just moves the cursor position.
>
> I believe, CTRL-W has always deleted (only until the position where you
> entered i
On Di, 14 Apr 2020, Tavis Ormandy wrote:
>
>
> On Tuesday, April 14, 2020 at 9:40:00 AM UTC-7, Christian Brabandt wrote:
>
>
> Sounds like you have started vim in compatible mode. :set nocp should
> fix it, but that enables a bunch of other options as well, so more
> specifically
On Tuesday, April 14, 2020 at 9:40:00 AM UTC-7, Christian Brabandt wrote:
>
>
> Sounds like you have started vim in compatible mode. :set nocp should
> fix it, but that enables a bunch of other options as well, so more
> specifically, use :set bs=2
>
>
>
Thanks, but I'm not in compatible mode.
On Di, 14 Apr 2020, Peng Yu wrote:
> I still get something printed. How to turn it off? So `< /dev/tty` is
> not needed anymore for both cases?
Use the :silent modifier?
Best
Christian
--
Ich verabscheue, was Sie sagen: ich werde Ihr Recht, es zu sagen, bis
zum Tod verteidigen.
>> I think it refers to painting the vim GUI, possibly switching to the
>> alternate screen, then clearing the (possibly alternate screen), then
>> possibly restoring the (non-)alternate screen, creating a "flash"
>> effect when scripting vim.
>
> Since this depends on the terminal, you can either
On Di, 14 Apr 2020, Tavis Ormandy wrote:
> Hello, I don't like the way that CTRL-W stops at the position you
> entered insert mode.
>
> For example, you can reproduce the behavior I'm talking about like this:
>
> * In normal mode, position the cursor at the end of a word, then enter
>inse
On 4/14/2020 03:54, Tony Mechelynck wrote:
• Which Vim version, including major.minor.patch? (As of this writing,
the latest version is 8.2.577)
I was using 8.2.480 but I had been having the problem for a while, just
hadn't been editing perl files so didn't worry about it. Uninstalled
8.2.48
Hello, I don't like the way that CTRL-W stops at the position you
entered insert mode.
For example, you can reproduce the behavior I'm talking about like this:
* In normal mode, position the cursor at the end of a word, then enter
insert mode.
* Type some letters to make the word longer, the
On Di, 14 Apr 2020, Tim Chase wrote:
> On 2020-04-14 10:01, Christian Brabandt wrote:
> > On Mo, 13 Apr 2020, Peng Yu wrote:
> >
> > > I use the following command to indent file in command line. But
> > > it blinks. Is there a way to let it not blink? Thanks.
> > >
> > > vim -n -X -E -c 'norma
On 2020-04-14 10:01, Christian Brabandt wrote:
> On Mo, 13 Apr 2020, Peng Yu wrote:
>
> > I use the following command to indent file in command line. But
> > it blinks. Is there a way to let it not blink? Thanks.
> >
> > vim -n -X -E -c 'normal gg=G' -c 'x' file.sh < /dev/tty
>
> What blinks?
On Tue, Apr 14, 2020 at 9:54 AM Knute Johnson wrote:
>
> If I attempt to edit a perl source file with "filetype plugin indent on"
> in my _vimrc file I get the following error:
>
> "test.pl" 4L, 69CJohnson\AppData\Local\Temp\VIo1F34.tmp was unexpected
> at this t
> ime.
>
> Error detected while pr
On Mo, 13 Apr 2020, Peng Yu wrote:
> I use the following command to indent file in command line. But it blinks. Is
> there a way to let it not blink? Thanks.
>
> vim -n -X -E -c 'normal gg=G' -c 'x' file.sh < /dev/tty
What blinks?
Best,
Christian
--
An Grundsätzen hält man nur fest, solang
Hi,
since the old certificate that has been used to sign the releases for
the vim/vim-win32-installer binaries is going to expire within 14 days,
a new certificate has been created by Signpath.
With the next release (probably tomorrow) that one will be used to sign
the binaries. However, since
If I attempt to edit a perl source file with "filetype plugin indent on"
in my _vimrc file I get the following error:
"test.pl" 4L, 69CJohnson\AppData\Local\Temp\VIo1F34.tmp was unexpected
at this t
ime.
Error detected while processing C:\Program Files
(x86)\Vim\vim82\ftplugin\perl.v
im:
li
27 matches
Mail list logo
