Re: an old "hack" of mine, shared for amusement

[Erik Falor]

On Tue, Apr 25, 2017 at 04:23:12PM -0400, Eli the Bearded wrote:
> Christian Brabandt wrote:
> > Are you saying, original Vi could be tricked to execute various commands
> > via modelines? That sounds pretty scary actually.
> 
> Still can, if you have real vi somewhere. (You can also embed arbitrary
> ex commands in tag files for real vi.)

I will say in my defense that the clue about the Vim 4.2 swap file was
a bit of a red herring, especially since Vim honors ex and vi's
modelines.

Anyhow, it's now time to test this with Traditional Vi

http://ex-vi.sourceforge.net/

-- 
Erik Falor
Registered Linux User #445632http://unnovative.net

-- 
-- 
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php

--- 
You received this message because you are subscribed to the Google Groups 
"vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_use+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


signature.asc
Description: PGP signature

Re: an old "hack" of mine, shared for amusement

[Eli the Bearded]

Christian Brabandt wrote:
> Are you saying, original Vi could be tricked to execute various commands
> via modelines? That sounds pretty scary actually.

Still can, if you have real vi somewhere. (You can also embed arbitrary
ex commands in tag files for real vi.)

Elijah

-- 
-- 
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php

--- 
You received this message because you are subscribed to the Google Groups 
"vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_use+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: an old "hack" of mine, shared for amusement

[Christian Brabandt]

Hi Eli!

On Di, 25 Apr 2017, Eli the Bearded wrote:

> Everyone seems to be missing it. rot13 solution for those interested.
> 
> This *hack* was designed to *not* work in vim.
> 
> It works in vi. It makes vi reopen the file with vim.
> 
> (And by-the-by, I have Vim 3.0 for Mac System 7. I found it for download
> last year when I was playing with the Basilisk II emulator. Vim 3: back
> when 'q' did the thing 'gq' does now. And 'Q' was unimplemented.) 

Are you saying, original Vi could be tricked to execute various commands 
via modelines? That sounds pretty scary actually.

Best,
Christian
-- 
Ein kluger Mann widerspricht nie einer Frau. Er wartet, bis sie es
selbst tut.
-- Humphrey Bogart

-- 
-- 
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php

--- 
You received this message because you are subscribed to the Google Groups 
"vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_use+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: an old "hack" of mine, shared for amusement

[Eli the Bearded]

Erik Falor wrote:
> I can report that this "hack" doesn't do anything interesting as of Vim 5.5.
> It doesn't complain about the pipe characters in the modelines, though.

Everyone seems to be missing it. rot13 solution for those interested.

Guvf *unpx* jnf qrfvtarq gb *abg* jbex va ivz.

Vg jbexf va iv. Vg znxrf iv erbcra gur svyr jvgu ivz.

(And by-the-by, I have Vim 3.0 for Mac System 7. I found it for download
last year when I was playing with the Basilisk II emulator. Vim 3: back
when 'q' did the thing 'gq' does now. And 'Q' was unimplemented.) 

Elijah
--
http://wayback.archive.org/web/19990422231919/http://www.qz.to/~eli/src/modeline.html

-- 
-- 
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php

--- 
You received this message because you are subscribed to the Google Groups 
"vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_use+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: an old "hack" of mine, shared for amusement

[Erik Falor]

On Tue, Apr 25, 2017 at 09:16:54AM +0200, Christian Brabandt wrote:
> 
> A while ago, I converted the old Vim CVS Repository to git and I made it 
> available here:
> https://bitbucket.org/vim-mirror/vim-ancient
> 
> #v+
> ~/vim-ancient$ git log --reverse |head -15
> commit 686757e4d2a46c8ab55c08c7a0ccd9d83d2465fb
> Author: Bram Moolenaar 
> Date:   Sun Dec 19 03:43:45 1999 +
> 
> Initial revision

I can report that this "hack" doesn't do anything interesting as of Vim 5.5.
It doesn't complain about the pipe characters in the modelines, though.

:version
VIM - Vi IMproved 5.5 (1999 Sep 19)
Compiled by fadein@viking2, with (+) or without (-):
+autocmd -browse ++builtin_terms +byte_offset +cindent +cmdline_compl 
+cmdline_info +comments +cryptv +cscope
+dialog_con +digraphs +emacs_tags +eval +ex_extra +extra_search +farsi 
+file_in_path -osfiletype +find_in_path +fork()
-GUI -hangul_input +insert_expand +langmap +linebreak +lispindent +menu 
+mksession +modify_fname +mouse +mouse_dec
-mouse_gpm +mouse_netterm +mouse_xterm +multi_byte -perl +quickfix -python 
+rightleft +scrollbind +smartindent -sniff
+statusline +syntax +tag_binary +tag_old_static -tag_any_white -tcl +terminfo 
+textobjects +title +user_commands
+visualextra +viminfo +wildignore +wildmenu +writebackup -X11 -xfontset -xim 
-xterm_clipboard -xterm_save
   system vimrc file: "$VIM/vimrc"
 user vimrc file: "$HOME/.vimrc"
  user exrc file: "$HOME/.exrc"
  fall-back for $VIM: "/usr/local/share/vim"
Compilation: gcc -c -I. -Iproto -DHAVE_CONFIG_H-g -O2 -Wall
Linking: gcc  -o vim -lncurses

-- 
Erik Falor
Registered Linux User #445632http://unnovative.net

-- 
-- 
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php

--- 
You received this message because you are subscribed to the Google Groups 
"vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_use+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


signature.asc
Description: PGP signature

Re: already at oldest change - how to suppress this message

[Tony Mechelynck]

On Tue, Apr 25, 2017 at 10:18 AM, Christian Brabandt  wrote:
> Hi Jim!
>
> On Mo, 24 Apr 2017, Jim Wilmore wrote:
>
>>I recently got a new laptop, so I decided I would install gvim80 after 
>> using gvim73 for many years.
>>As an old Unix user from the 70s onward, I have quite a lot of 
>> customization, and when I discovered Gvim, my customization quadrupled.
>>I finally have my new machine running gvim about the same as before. I 
>> had to set the guifont, but most everything else worked out. However, I keep 
>> getting the message "Already at oldest change" when I open a file. I am 
>> guessing this is related either to version control (which I handle 
>> independently when I need it) or some sort of temporary backup file (which I 
>> have turned off, at least in previous customizations).
>>How do I turn off this message?!? I have browsed through the possible 
>> settings, and have found nothing yet. Help, please...
>
> Looks like some configuration is issuing an undo command when it
> shouldn't. Check your autocommands or your plugins. Also see the faq:
> https://vimhelp.appspot.com/vim_faq.txt.html#faq-2.5
>
>
> Best,
> Christian

Yes, "Already at oldest change" is a message from the Normal-mode u
(undo) command or the :u[ndo] Ex-command when they can't do anything
because there is no earlier stored history for them to go to. I find
that message extremely useful when I try to (manually) go back in
history and nothing happens.

See also the 'history' and 'viminfo' options.

Best regards,
Tony.

-- 
-- 
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php

--- 
You received this message because you are subscribed to the Google Groups 
"vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_use+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Vim Improvement suggester

[Shawn H Corey]

On Tue, 25 Apr 2017 04:12:46 -0700 (PDT)
Patrik Iselind  wrote:

> Even if they lack context you can still figure out things like "You
> use j and k to move around a lot. A faster and less error prone way
> would be using seaching for example.". This could be one example of
> that the feature would bring to the table.

I use / (search) to move around a lot. It is the fastest way I found (so
far). ☺

The second fastest is to use an after/ftplugin to preset marks.


-- 
Don't stop where the ink does.

Shawn H Corey

-- 
-- 
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php

--- 
You received this message because you are subscribed to the Google Groups 
"vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_use+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Vim Improvement suggester

[Patrik Iselind]

Den onsdag 19 april 2017 kl. 10:22:25 UTC+2 skrev ZyX:
> 
> 1. Parsing , see :h 'verbose' and :h 'verbosefile'. Should
> only work for Ex commands, but not for normal-mode commands.
> 2. Recording your input in `-w {scriptout}` and parsing to guess where
> are commands there and where is regular input.
> 
> Though I am not thinking this would be a good idea: based on my
> experience Vim commands are normally not a bottleneck, designing what
> and how to write is.
> 


The bottle neck for me is usually how i change my text. When i learn a new 
feature/command in Vim i usually think something along the lines of "I would 
have gained so much if someone had told me about this earlier". So abstracting 
the someone into something might be a good enough approximation.

Vim fluency would be attained faster with a bit of help. As we all know, the 
learning curve of Vim is not flat...

-- 
-- 
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php

--- 
You received this message because you are subscribed to the Google Groups 
"vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_use+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Vim Improvement suggester

[Patrik Iselind]

Den onsdag 19 april 2017 kl. 11:25:38 UTC+2 skrev MarcWeber:
> Brams advice was
> 1) watch yourself
> 2) look at what takes most of you time
> 3) use mailinglist or chat to ask how to do things faster.
> 
> I've put some ideas here:
> https://github.com/MarcWeber/vim-addon-manager/blob/master/autoload/sample_vimrc_for_new_users.vim
> 
> "The commands" you wan to record lack context, so no human/ai would be
> able to suggest "how to do things better" without knowing your task.
> 
> MfG
> Marc Weber

Even if they lack context you can still figure out things like "You use j and k 
to move around a lot. A faster and less error prone way would be using seaching 
for example.". This could be one example of that the feature would bring to the 
table.

I'm not saying it needs a 100% coverage, just enough to get over the biggest 
hurdles.

// Patrik

-- 
-- 
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php

--- 
You received this message because you are subscribed to the Google Groups 
"vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_use+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: already at oldest change - how to suppress this message

[Christian Brabandt]

Hi Jim!

On Mo, 24 Apr 2017, Jim Wilmore wrote:

>I recently got a new laptop, so I decided I would install gvim80 after 
> using gvim73 for many years.
>As an old Unix user from the 70s onward, I have quite a lot of 
> customization, and when I discovered Gvim, my customization quadrupled. 
>I finally have my new machine running gvim about the same as before. I had 
> to set the guifont, but most everything else worked out. However, I keep 
> getting the message "Already at oldest change" when I open a file. I am 
> guessing this is related either to version control (which I handle 
> independently when I need it) or some sort of temporary backup file (which I 
> have turned off, at least in previous customizations).
>How do I turn off this message?!? I have browsed through the possible 
> settings, and have found nothing yet. Help, please...

Looks like some configuration is issuing an undo command when it 
shouldn't. Check your autocommands or your plugins. Also see the faq: 
https://vimhelp.appspot.com/vim_faq.txt.html#faq-2.5


Best,
Christian
-- 
Ich bin bereit überall hinzugehen, wenn es nur vorwärts ist.
-- David Livingstone

-- 
-- 
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php

--- 
You received this message because you are subscribed to the Google Groups 
"vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_use+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: an old "hack" of mine, shared for amusement

[Christian Brabandt]

On Mo, 24 Apr 2017, Erik Falor wrote:

> Eli did mention that he had been running Vim version 4.2. Perhaps
> modelines worked differently back then?
> 
> The oldest Vim source code I could find in a brief search is version
> 6.4. Does anybody know of a way to find a version that's even older
> than that?

A while ago, I converted the old Vim CVS Repository to git and I made it 
available here:
https://bitbucket.org/vim-mirror/vim-ancient

#v+
~/vim-ancient$ git log --reverse |head -15
commit 686757e4d2a46c8ab55c08c7a0ccd9d83d2465fb
Author: Bram Moolenaar 
Date:   Sun Dec 19 03:43:45 1999 +

Initial revision

commit d8a836d4df71284a494011056263b98972ae6823
Author: Bram Moolenaar 
Date:   Sun Dec 19 03:50:09 1999 +

Patch 5.5.001
Problem:Configure in the top directory did not pass on an argument with 
a
space correctly.  For example "./configure --previs="/My home".
(Stephane Chazelas)
Solution:   Use '"$@"' instead of '$*' to pass on the arguments.
#v-


Best,
Christian
-- 
Es gibt zwei Arten von Menschen: Solche die Glück haben und solche wie mich.

-- 
-- 
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php

--- 
You received this message because you are subscribed to the Google Groups 
"vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_use+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.