On 2022-01-03, Brian L. Matthews wrote:
> On 1/3/22 1:55 PM, Lifepillar wrote:
> >On 2022-01-03, Manfred Lotz wrote:
> >>Another point might be interesting. In the undo directory there are
> >>undo files where the real files don't exist any longer. Not sure if
> >>there is some cleanup procedure
On 1/3/22 1:55 PM, Lifepillar wrote:
On 2022-01-03, Manfred Lotz wrote:
Another point might be interesting. In the undo directory there are
undo files where the real files don't exist any longer. Not sure if
there is some cleanup procedure avalaible.
I use this command to remove undo files
On Mon, 3 Jan 2022, Lifepillar wrote:
Do you mean, to navigate the (not necessarily persistent) undo history?
Yes but also to have the undoes stored somewhere.
Not sure I understand: persistent undo is a built-in Vim feature (see
Manfred's post). Are you looking for something that Vim
On 2022-01-03, Walter Cazzola wrote:
> On Mon, 3 Jan 2022, Lifepillar wrote:
>
>> On 2022-01-03, Walter Cazzola wrote:
>>> Out of curiosity: which plugin are you using for the persistent undo.
>>
>> Do you mean, to navigate the (not necessarily persistent) undo history?
>
> Yes but also to have
On 2022-01-03, Manfred Lotz wrote:
> Another point might be interesting. In the undo directory there are
> undo files where the real files don't exist any longer. Not sure if
> there is some cleanup procedure avalaible.
I use this command to remove undo files that haven't changed in a long
time:
On 1/3/22 10:07 PM, Walter Cazzola wrote:
> On Mon, 3 Jan 2022, Manfred Lotz wrote:
>
>> On 1/3/22 5:53 PM, Walter Cazzola wrote:
>>> Out of curiosity: which plugin are you using for the persistent undo.
>
>>> I have tried (few years ago) a few but they were quite unsatisfactory and
>>> being
On Mon, 3 Jan 2022, Manfred Lotz wrote:
On 1/3/22 5:53 PM, Walter Cazzola wrote:
Out of curiosity: which plugin are you using for the persistent undo.
I have tried (few years ago) a few but they were quite unsatisfactory and
being something I feel necessary I would like to get advice.
On Mon, 3 Jan 2022, Lifepillar wrote:
On 2022-01-03, Walter Cazzola wrote:
Out of curiosity: which plugin are you using for the persistent undo.
Do you mean, to navigate the (not necessarily persistent) undo history?
Yes but also to have the undoes stored somewhere.
I use undotree
On 1/3/22 5:53 PM, Walter Cazzola wrote:
> Out of curiosity: which plugin are you using for the persistent undo.
>
> I have tried (few years ago) a few but they were quite unsatisfactory and
> being something I feel necessary I would like to get advice.
>
Same as Lifepillar I use undotree.
Den mån 3 jan. 2022 18:34Bram Moolenaar skrev:
>
> > On 2022-01-03, Marvin Renich wrote:
> > > Don't bother with the
> >
> > > import MyClass from "myclass.vim"
> > > import {someValue, MyClass} from "thatscript.vim"
> > >
> > > syntax, and only provide
> > >
> > > import "myclass.vim"
>
On 2022-01-03, Walter Cazzola wrote:
> Out of curiosity: which plugin are you using for the persistent undo.
Do you mean, to navigate the (not necessarily persistent) undo history?
I use undotree (https://github.com/mbbill/undotree). I prefer it over
other choices mainly because it is pure Vim
> On 2022-01-03, Marvin Renich wrote:
> > Don't bother with the
>
> > import MyClass from "myclass.vim"
> > import {someValue, MyClass} from "thatscript.vim"
> >
> > syntax, and only provide
> >
> > import "myclass.vim"
> > import "myclass.vim" as Other
> >
> > and require use of the
hello everyone and thanks to the vim contributors,
Le Mon, Jan 03, 2022 at 11:04:32AM +, Bram Moolenaar a écrit :
> > comments suggested to reverse the import syntax so that the imported
> > script is named first and the imported entities next. A rationale for
> > this is that it would help
Out of curiosity: which plugin are you using for the persistent undo.
I have tried (few years ago) a few but they were quite unsatisfactory and
being something I feel necessary I would like to get advice.
Walter
On Fri, 31 Dec 2021, Bram Moolenaar wrote:
Manfred Lotz wrote:
I have
On Mon, Jan 3, 2022, 11:23 Lifepillar wrote:
> On 2022-01-03, Marvin Renich wrote:
> > Don't bother with the
>
> > import MyClass from "myclass.vim"
> > import {someValue, MyClass} from "thatscript.vim"
> >
> > syntax, and only provide
> >
> > import "myclass.vim"
> > import
On 2022-01-03, Marvin Renich wrote:
> Don't bother with the
> import MyClass from "myclass.vim"
> import {someValue, MyClass} from "thatscript.vim"
>
> syntax, and only provide
>
> import "myclass.vim"
> import "myclass.vim" as Other
>
> and require use of the namespace prefix:
>
>
> --
> $ echo pizza > /dev/oven
>
Totally OT, but Bram's signature file is amazing. Yet another reason to
thank him. I shall use that as an example when explaining output
mechanisms from now on.
--
--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below
Marvin Renich wrote:
> * Bram Moolenaar [220103 07:07]:
> >
> > > On 2021-12-30, Bram Moolenaar wrote:
> > > > If you have remarks on something in Vim9 script that you think should be
> > > > different, speak up now! Soon we'll only make backwards compatible
> > > > changes to avoid
* Bram Moolenaar [220103 07:07]:
>
> > On 2021-12-30, Bram Moolenaar wrote:
> > > If you have remarks on something in Vim9 script that you think should be
> > > different, speak up now! Soon we'll only make backwards compatible
> > > changes to avoid breaking existing plugins.
> >
> > There
> ["Followup-To:" header set to gmane.editors.vim.]
> On 2021-12-30, Bram Moolenaar wrote:
> > The work on Vim9 script is coming to a point where the syntax and
> > semantics are practially done. There might be some more tests
> > uncovering problems that need to be fixed and perhaps some tiny
["Followup-To:" header set to gmane.editors.vim.]
On 2021-12-30, Bram Moolenaar wrote:
> The work on Vim9 script is coming to a point where the syntax and
> semantics are practially done. There might be some more tests
> uncovering problems that need to be fixed and perhaps some tiny tweaks,
>
21 matches
Mail list logo
