Mr. Mechelynck
On 28/10/2019 02:01, Tony Mechelynck wrote:
> To set the n suboption in 'viminfo', RTFM:
No, I will not "Read The Fucking Manual".
Kindly keep your course language to yourself.
Kind Regards,
Andre Sihera.
--
--
You received this message from the "vim_dev" maillist.
Do not top
Hi Dominique,
On 26/10/2019 19:10, Dominique Pellé wrote:
> Sihera Andre wrote:
>
>> Hi Christian,
>>
>>
>> On 25/10/2019 17:53, Christian Brabandt wrote:
>>> On Fr, 25 Okt 2019, Sihera Andre wrote:
>>>
>>>> The reason I don't
Hi James and Christian,
On 27/10/2019 23:56, Andre Sihera wrote:
> Hi James,
>
>
> On 26/10/2019 21:26, James McCoy wrote:
>> On Fri, Oct 25, 2019 at 09:54:33AM +, Sihera Andre wrote:
>>> On 25/10/2019 18:24, Christian Brabandt wrote:
>>>> On Fr, 2
Hi James,
On 26/10/2019 21:26, James McCoy wrote:
> On Fri, Oct 25, 2019 at 09:54:33AM +0000, Sihera Andre wrote:
>> On 25/10/2019 18:24, Christian Brabandt wrote:
>>> On Fr, 25 Okt 2019, Sihera Andre wrote:
>>>> I think there should be another debate enabling .vi
Hi Christian,
On 26/10/2019 16:52, Christian Brabandt wrote:
> On Fr, 25 Okt 2019, Sihera Andre wrote:
>
>> HI Christian,
>>
>>
>> On 25/10/2019 18:24, Christian Brabandt wrote:
>>> On Fr, 25 Okt 2019, Sihera Andre wrote:
>>>
>>>>
*** Word spacing fixed. Last transmission had corrupted word spacing ***
Hi Bram,
On 25/10/2019 22:17, Bram Moolenaar wrote:
> Sihera Andre wrote:
>
>>
>> However, unlike most systems which
>> typically encrypt the *entire* partition (
Hi Bram,
On 25/10/2019 22:17, Bram Moolenaar wrote:
> Sihera Andre wrote:
>
>>
>>However, unlike most systems which
>> typically encrypt the *entire* partition (e.g., all of "/", all of "/home"
>> or all of "
HI Christian,
On 25/10/2019 18:24, Christian Brabandt wrote:
> On Fr, 25 Okt 2019, Sihera Andre wrote:
>
>> Except that .viminfo, which I would like to relocate to my encrypted
>> partitions, cannot be stored there because it can't be symbolic linked.
>>
>>
Hi Christian,
On 25/10/2019 17:53, Christian Brabandt wrote:
> On Fr, 25 Okt 2019, Sihera Andre wrote:
>
>> The reason I don't "simply" do "make install" is because, in the past,
>> what was installed from a locally checked-out repository and what was
&
Hi Christian,
On 25/10/2019 15:59, Christian Brabandt wrote:
> On Fr, 25 Okt 2019, Christian Brabandt wrote:
>
>> On Fr, 25 Okt 2019, Sihera Andre wrote:
>>
>>> Hello all,
>>>
>>> The "backupcopy" option does not appear to be working as
&g
Hi Christian,
On 25/10/2019 15:31, Christian Brabandt wrote:
> On Fr, 25 Okt 2019, Sihera Andre wrote:
>
>> I realised just now I asked a silly question regarding a HEAD version
>> of the runtime when it was staring right at me.
>>
>> I rebuilt the HEAD version o
Hi Tony,
On 25/10/2019 15:38, Tony Mechelynck wrote:
> On Fri, Oct 25, 2019 at 7:36 AM Sihera Andre
> wrote:
>> Hi Tony,
>>
>>
>> On 25/10/2019 13:55, Tony Mechelynck wrote:
>>> On Fri, Oct 25, 2019 at 6:31 AM Sihera Andre
>>> wrote:
>>&
Hi Tony,
On 25/10/2019 13:55, Tony Mechelynck wrote:
> On Fri, Oct 25, 2019 at 6:31 AM Sihera Andre
> wrote:
>> On 25/10/2019 13:06, Andre Sihera wrote:
>>> Hello all,
>>>
>>> The "backupcopy" option does not appear to be working as
>>>
On 25/10/2019 13:06, Andre Sihera wrote:
> Hello all,
>
> The "backupcopy" option does not appear to be working as
> documented in the version of VIM I have built locally. As the
> run-time contains online help for the feature I assume that
> my version of VIM supports it, or does it?
>
> Binary: 8
On 25/10/2019 11:05, Andre Sihera wrote:
> Tony,
> Christian,
> Sorry for the delayed response.
>
> On 24/10/2019 11:07, Tony Mechelynck wrote:
>>
>> Runtime files ought to be of a version as close as possible to the
>> executable with which they are used. Using 8.0 runtime files with a
>> 8.1 ex
Hello all,
The "backupcopy" option does not appear to be working as
documented in the version of VIM I have built locally. As the
run-time contains online help for the feature I assume that
my version of VIM supports it, or does it?
Binary: 8.0.1766
Runtime: 8.0.1766
(full information at bottom)
Tony,
Christian,
Sorry for the delayed response.
On 24/10/2019 11:07, Tony Mechelynck wrote:
>
> Runtime files ought to be of a version as close as possible to the
> executable with which they are used. Using 8.0 runtime files with a
> 8.1 executabe might work — or it might not.
>
>
Up until now I
Hello all,
Apologies for posting to the mailing list before filing a bug report
but I just wanted to make sure that I was facing a bug and not a silly
build error of some kind.
The problem is that while editing scripts (e.g., .bashrc), or anything
where the file type is set to "sh", when I cursor
On 29/07/19 04:02, tooth pik wrote:
> i love and use the CTRL-E and CTRL-Y scrolling commands so much i have
> them mapped to F10 and F11 in my ~/.vimrc:
>
> nnoremap
> inoremap
> nnoremap
> inoremap
>
> just today i noticed both up and down are impeded if i happen to be in
> insert mode wh
On 15/03/19 05:37, Bram Moolenaar wrote:
> Andre Sihera wrote:
>
>> I'm using a fairly old version of ViM (7.3) on Ubuntu so I wondered if
>> this problem
>> isalready known about and maybe fixed in a newer version.
>>
>> The problem is that the clipboard contents appear to be getting
>> corrupted
Hi all,
I'm using a fairly old version of ViM (7.3) on Ubuntu so I wondered if
this problem
isalready known about and maybe fixed in a newer version.
The problem is that the clipboard contents appear to be getting
corrupted during a
cut/paste using the '*' register.
Way to reproduce:
1) Open
21 matches
Mail list logo
