On May 24, 1:06 pm, Bram Moolenaar wrote:
> I have also changed the MS-Windows installer. It should now work in
> Windows 7. I also tried making the "Edit with Vim" context menu work
> for 64 bit systems, but it doesn't appear to work yet.
>
> You can try the self-installing executable:
> ftp:/
On Mon, May 24, 2010 at 3:06 PM, Bram Moolenaar wrote:
>
> As you may have noticed, I have added the persistent undo patch
> yesterday. The core of this was done by Jordan Lewis.
> This means you can make changes to a file, quit Vim, edit that same file
> and undo the previous changes.
>
> I hav
Nico Raffo wrote:
> On May 24, 1:06=A0pm, Bram Moolenaar wrote:
> > I have also changed the MS-Windows installer. =A0It should now work in
> > Windows 7. =A0I also tried making the "Edit with Vim" context menu work
> > for 64 bit systems, but it doesn't appear to work yet.
> >
> > You can try th
Jordan Lewis wrote:
> --0016e68ee46947c7a104875ce992
> Content-Type: text/plain; charset=ISO-8859-1
>
> On Mon, May 24, 2010 at 3:06 PM, Bram Moolenaar wrote:
>
> >
> > As you may have noticed, I have added the persistent undo patch
> > yesterday. The core of this was done by Jordan Lewis.
>
Bram Moolenaar schrob am 24.05.2010 22:56:
I suppose most people will want Python 2.6. I'll see if I manage to
make that work. You can try it yourself, if you like.
It compiles without any problem in my builds. :-)
--
You received this message from th
On Mon, May 24, 2010 at 10:56:59PM +0200, Bram Moolenaar wrote:
>
> Jordan Lewis wrote:
> > I suppose the argument could be made that the user who has added undo
> > persistence to her vimrc would have read enough of the documentation to know
> > that she must also set undodir if she doesn't want
On 24/05/10 22:30, Jordan Lewis wrote:
[...]
I am a bit concerned with your decision to write undo files to the
current directory by default, though. I think that it is "impolite" to
users to have Vim store its state (especially at the
1-statefile-per-file rate that undo persistence uses) directl
On Mon, May 24, 2010 at 4:39 PM, Tony Mechelynck <
antoine.mechely...@gmail.com> wrote:
> On 24/05/10 22:30, Jordan Lewis wrote:
> [...]
>
> I am a bit concerned with your decision to write undo files to the
>> current directory by default, though. I think that it is "impolite" to
>> users to hav
On Mon, May 24, 2010 at 4:23 PM, James Vega wrote:
> On Mon, May 24, 2010 at 10:56:59PM +0200, Bram Moolenaar wrote:
> >
> > Jordan Lewis wrote:
> > > I suppose the argument could be made that the user who has added undo
> > > persistence to her vimrc would have read enough of the documentation t
On Mon, May 24, 2010 at 10:56:59PM +0200, Bram Moolenaar wrote:
[..]
I suppose most people will want Python 2.6. I'll see if I manage to
make that work. You can try it yourself, if you like.
I also have a patch to support Python 3. We'll have to see if
dynamically loading both will work. I
On 25 May 2010 06:06, Bram Moolenaar wrote:
>
> As you may have noticed, I have added the persistent undo patch
> yesterday.
There is a minor typo in the doc for 'persistent-undo'. Patch attached.
--
You received this message from the "vim_dev" maillist.
Do not top-post! Type your reply below t
On Mon, May 24, 2010 10:06 pm, Bram Moolenaar wrote:
> I also changed it to put the undofile with the edited file. That should
> work, as writing a file usually means the undofile can be written there
> as well. It's possible to change this with the 'undodir' option.
Is this a good idea? General
On 24/05/10 23:52, Jordan Lewis wrote:
[...]
I should have worded my post better - I did mean the directory of the
file as you indicate. And the patch doesn't blindly name all undo files
the same if they have the same filename - with a common undo directory,
the files will be named path_to_vim73_
On Tue, May 25, 2010 at 01:21:43PM +0200, Tony Mechelynck wrote:
> On 24/05/10 23:52, Jordan Lewis wrote:
> [...]
> >I should have worded my post better - I did mean the directory of the
> >file as you indicate. And the patch doesn't blindly name all undo files
> >the same if they have the same fil
James Vega wrote:
> On Mon, May 24, 2010 at 10:56:59PM +0200, Bram Moolenaar wrote:
> >
> > Jordan Lewis wrote:
> > > I suppose the argument could be made that the user who has added undo
> > > persistence to her vimrc would have read enough of the
> > > documentation to know that she must also
On Tue, May 25, 2010 at 02:29:23PM +0200, Bram Moolenaar wrote:
> James Vega wrote:
> > Are the undo files supposed to be hidden when 'undodir' is not the
> > current directory? If so, that's not currently the case.
>
> When putting undo files with the edited files they are made hidden, just
> li
On 25/05/10 14:19, James Vega wrote:
On Tue, May 25, 2010 at 01:21:43PM +0200, Tony Mechelynck wrote:
On 24/05/10 23:52, Jordan Lewis wrote:
[...]
I should have worded my post better - I did mean the directory of the
file as you indicate. And the patch doesn't blindly name all undo files
the sa
Christian Brabandt wrote:
> On Mon, May 24, 2010 10:06 pm, Bram Moolenaar wrote:
> > I also changed it to put the undofile with the edited file. That should
> > work, as writing a file usually means the undofile can be written there
> > as well. It's possible to change this with the 'undodir' o
On Tue, May 25, 2010 at 12:48, Christian Brabandt wrote:
> On Mon, May 24, 2010 10:06 pm, Bram Moolenaar wrote:
>> I also changed it to put the undofile with the edited file. That should
>> work, as writing a file usually means the undofile can be written there
>> as well. It's possible to chang
> That said, I think persistent undo is more or less useless and, well,
> just a big pile of potential problems. Persistent undo is in the
> version control system, not in the editor.
I agree with that. This would probably be best left to versionning systems.
Shouldn't Vim be used for purely te
Michael Wookey wrote:
> On 25 May 2010 06:06, Bram Moolenaar wrote:
> >
> > As you may have noticed, I have added the persistent undo patch
> > yesterday.
>
> There is a minor typo in the doc for 'persistent-undo'. Patch attached.
Thanks!
--
Bare feet magnetize sharp metal objects so they po
Nikolai Weibull wrote:
> That said, I think persistent undo is more or less useless and, well,
> just a big pile of potential problems. Persistent undo is in the
> version control system, not in the editor.
I think this is a bit harsh. Not every file is in version control.
And even if you do us
2010/5/25 Dominique Pellé :
> Nikolai Weibull wrote:
>> That said, I think persistent undo is more or less useless and, well,
>> just a big pile of potential problems. Persistent undo is in the
>> version control system, not in the editor.
> I think this is a bit harsh.
And I think persistent u
Hi Nikolai!
On Di, 25 Mai 2010, Nikolai Weibull wrote:
> 2010/5/25 Dominique Pellé :
> > Nikolai Weibull wrote:
> >> That said, I think persistent undo is more or less useless and, well,
> >> just a big pile of potential problems. Persistent undo is in the
> >> version control system, not in the
On Tue, May 25, 2010 at 19:42, Christian Brabandt wrote:
> On Di, 25 Mai 2010, Nikolai Weibull wrote:
>> 2010/5/25 Dominique Pellé :
>> > Nikolai Weibull wrote:
>> >> That said, I think persistent undo is more or less useless and, well,
>> >> just a big pile of potential problems. Persistent un
On Tue, 25 May 2010, Nikolai Weibull wrote:
And no one forced you to defend this feature.
True, nobody is forcing anybody to defend the feature, but what do you
expect to happen when you complain about it?
Why does everyone have to come in and say basically the same thing
in response to my
On Tue, May 25, 2010 at 21:04, Christian J. Robinson wrote:
> On Tue, 25 May 2010, Nikolai Weibull wrote:
>
>> And no one forced you to defend this feature.
>
> True, nobody is forcing anybody to defend the feature, but what do you
> expect to happen when you complain about it?
I figured that “Th
2010/5/25 Dominique Pellé :
> Does anybody use all Vim features? :-)
Does anybody actually know all Vim features? :-)
Sometimes I accidentally quit Vim while editing a file (hitting w and
q at the same time when saving for instance), losing the undo history
at the same time. I can certainly see a
On Tue, May 25, 2010 at 2:27 PM, Nikolai Weibull wrote:
> I figured that “That said, I think persistent undo is more or less
> useless and, well, just a big pile of potential problems. Persistent
> undo is in the version control system, not in the editor.” is me
> stating an opinion about it, no
On Tue, May 25, 2010 at 22:38, Jordan Lewis wrote:
> For example, pretend you're developing the ultimate novel Vim feature, but
> you've caused a bug, and want to trace it in gdb. You edit Vim's makefile to
> enable -g in CFLAGS, recompile, track down the bug, and want to compile a
> release vers
Hi Bram!
On Di, 25 Mai 2010, Bram Moolenaar wrote:
> Christian Brabandt wrote:
>
> This completely depends on what you are doing. When a file has been
> edited by someone else, using Vim, you can undo his changes. That can
> be very useful. On the other hand, the undo file will reveal anythin
On 25/05/10 19:42, Christian Brabandt wrote:
Hi Nikolai!
On Di, 25 Mai 2010, Nikolai Weibull wrote:
2010/5/25 Dominique Pellé:
Nikolai Weibull wrote:
That said, I think persistent undo is more or less useless and, well,
just a big pile of potential problems. Persistent undo is in the
versio
On 25/05/10 22:13, François Ingelrest wrote:
2010/5/25 Dominique Pellé:
Does anybody use all Vim features? :-)
Does anybody actually know all Vim features? :-)
Sometimes I accidentally quit Vim while editing a file (hitting w and
q at the same time when saving for instance), losing the undo h
On May 26, 7:32 am, Tony Mechelynck
wrote:
>
> As for floating point numbers, I constantly use Vim as a floating-point
> calculator; I wouldn't say it's a useless feature. Not a /necessary/ one
> -- I could do without the trig and exp/log functions
When floating point was included, I thought it
On Thu, May 27, 2010 at 17:23, Ben Fritz wrote:
> On May 26, 7:32 am, Tony Mechelynck
> wrote:
>> As for floating point numbers, I constantly use Vim as a floating-point
>> calculator; I wouldn't say it's a useless feature. Not a /necessary/ one
>> -- I could do without the trig and exp/log fun
> When editing a file over a network or a removable media (USB stick) it's
> very easy to misplace the undo file. Also, when a file is edited by
> several people, or the same person with different login names or from
> different systems, the undo file would go in the wrong place. Also
> problems
Milan Vancura wrote:
> > When editing a file over a network or a removable media (USB stick) it's
> > very easy to misplace the undo file. Also, when a file is edited by
> > several people, or the same person with different login names or from
> > different systems, the undo file would go in the
On Tuesday 25 May 2010 13:11:34 Milan Vancura wrote:
> > When editing a file over a network or a removable media (USB stick) it's
> > very easy to misplace the undo file. Also, when a file is edited by
> > several people, or the same person with different login names or from
> > different systems,
On 25/05/10 22:37, Bram Moolenaar wrote:
[...]
The undo files are hidden, all version control systems I know will
ignore them. E.g. swap files are normally not a problem.
[...]
For a counterexample, Mercurial tracks files regardless of an initial
dot: .hgignore is specifically mentioned as tr
Tony Mechelynck wrote:
> On 25/05/10 22:37, Bram Moolenaar wrote:
> [...]
> > The undo files are hidden, all version control systems I know will
> > ignore them. E.g. swap files are normally not a problem.
> [...]
>
> For a counterexample, Mercurial tracks files regardless of an initial
> dot:
On May 25, 3:37 pm, Bram Moolenaar wrote:
> This is moot though, a file edited by several people is very unusual,
> and if it does happen an undo file won't be very useful. Better not
> enable the undofile option for this kind of file.
>
I haven't had time to try out the Vim 7.3 stuff. Is pers
On Thu, 27 May 2010, Ben Fritz wrote:
Is persistent undo a buffer-local option? It sounds like perhaps it
should be, so that users can easily turn it on and off on a per-file
basis.
I agree that this is an option that should be possible to set locally.
Setting it with ":set" should default t
On Thu, May 27, 2010 at 11:02 AM, Ben Fritz wrote:
> On May 25, 3:37 pm, Bram Moolenaar wrote:
>> This is moot though, a file edited by several people is very unusual,
>> and if it does happen an undo file won't be very useful. Better not
>> enable the undofile option for this kind of file.
>>
>
Ben Fritz wrote:
> On May 25, 3:37=A0pm, Bram Moolenaar wrote:
> > This is moot though, a file edited by several people is very unusual,
> > and if it does happen an undo file won't be very useful. =A0Better not
> > enable the undofile option for this kind of file.
> >
>
> I haven't had time to
Bram Moolenaar, 2010-05-26 22:59:
>
> Tony Mechelynck wrote:
>
> > On 25/05/10 22:37, Bram Moolenaar wrote:
> > [...]
> > > The undo files are hidden, all version control systems I know will
> > > ignore them. E.g. swap files are normally not a problem.
> > [...]
> >
> > For a counterexample, M
On 28/05/10 01:54, Markus Heidelberg wrote:
Bram Moolenaar, 2010-05-26 22:59:
Tony Mechelynck wrote:
On 25/05/10 22:37, Bram Moolenaar wrote:
[...]
The undo files are hidden, all version control systems I know will
ignore them. E.g. swap files are normally not a problem.
[...]
For a count
On Fri, May 28, 2010 at 2:59 AM, Tony Mechelynck wrote:
>> ...
>
> I would add not only .*.swp but even .*.sw? (to ignore .swo .swn etc.),
> src/auto/config.mk (which is regenerated by configure from the
> config.mk.dist and a couple of others) and runtime/doc/tags (which is
> regenerated by make i
Tony Mechelynck, 2010-05-28 02:59:
> On 28/05/10 01:54, Markus Heidelberg wrote:
> > You can still add something like .*.swp to .hgignore for the swap files.
>
> I would add not only .*.swp but even .*.sw? (to ignore .swo .swn etc.),
Yes, that would make sense.
> src/auto/config.mk (which is re
On Thu, May 27, 2010 at 3:21 PM, Bram Moolenaar wrote:
>
> I have not heard a request for 'backup' to be buffer-local. We do have
> the 'backupskip' option. Would we need a 'undofileskip' option? And
> perhaps a "undofileapply" option for the opposite? I think using the
> buffer-local option i
49 matches
Mail list logo
