[arch-general] reconfiguring vi to work like it did before the last update?
Listmates, One are where I can use help is vi configuration. With the latest updates to vi and I guess readline, vi behaves very differently than it did just before the update. Specifically, the screen flashes white/black when the cursor is in column 1 if a left cursor is pressed or if vi toggles itself out of input mode. How can I get rid of the flashing and get rid of vi taking itself out of input/replace mode when it gets to column 1? The current behavior is better than when I first tried it several weeks ago, but it is still way different from any vi I have used before. Anybody got a handy reference for handling vi changes in the latest version? -- David C. Rankin, J.D.,P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 Telephone: (936) 715-9333 Facsimile: (936) 715-9339 www.rankinlawfirm.com
On Mon, Jul 13, 2009 at 8:00 AM, David C. Rankin<drankinatty@suddenlinkmail.com> wrote:
Listmates,
One are where I can use help is vi configuration. With the latest updates to vi and I guess readline, vi behaves very differently than it did just before the update. Specifically, the screen flashes white/black when the cursor is in column 1 if a left cursor is pressed or if vi toggles itself out of input mode.
How can I get rid of the flashing and get rid of vi taking itself out of input/replace mode when it gets to column 1?
The current behavior is better than when I first tried it several weeks ago, but it is still way different from any vi I have used before. Anybody got a handy reference for handling vi changes in the latest version?
Is it vi or vim? Which version? What terminal are you running it in? I run vim (7.2.65-1.1) in either gnome-terminal or xterm and I have none of these issues. /M -- Magnus Therning (OpenPGP: 0xAB4DFBA4) magnus＠therning．org Jabber: magnus＠therning．org http://therning.org/magnus identi.ca|twitter: magthe
i think you're using [testing] and then use vi-1.79 which is nvi. and not the vi you know which was a stripped down version of vim nvi behave like the original vi and not like vim. i think there's nothing you can do about this to the dev: why not rename vi package to nvi ?
On Monday 13 July 2009 11:49, solsTiCe d'Hiver wrote:
to the dev: why not rename vi package to nvi ?
+1 to that -- If we could implement a physical system with the storage capacity that matches the 128-bit address range of ZFS, that we would "literally evaporate all the oceans on earth". [...] Okay. The oceans are history! So are we. But ZFS will live forever. Dave Brillhart
On Mon, Jul 13, 2009 at 10:18 AM, Ed Jobs<oloringr@gmail.com> wrote:
On Monday 13 July 2009 11:49, solsTiCe d'Hiver wrote:
to the dev: why not rename vi package to nvi ?
+1 to that
Sounds like a good idea, especially since nvi _isn't_ vi in the strictest sense. /M -- Magnus Therning (OpenPGP: 0xAB4DFBA4) magnus＠therning．org Jabber: magnus＠therning．org http://therning.org/magnus identi.ca|twitter: magthe
On Mon, Jul 13, 2009 at 05:32, Magnus Therning<magnus@therning.org> wrote:
On Mon, Jul 13, 2009 at 10:18 AM, Ed Jobs<oloringr@gmail.com> wrote:
On Monday 13 July 2009 11:49, solsTiCe d'Hiver wrote:
to the dev: why not rename vi package to nvi ?
+1 to that
Sounds like a good idea, especially since nvi _isn't_ vi in the strictest sense.
Neither is vim. To my understanding, nvi emulates original vi more closely than the old vi package.
2009/7/13 Magnus Therning <magnus@therning.org>
On Mon, Jul 13, 2009 at 10:18 AM, Ed Jobs<oloringr@gmail.com> wrote:
On Monday 13 July 2009 11:49, solsTiCe d'Hiver wrote:
to the dev: why not rename vi package to nvi ?
+1 to that
Sounds like a good idea, especially since nvi _isn't_ vi in the strictest sense.
Neither was the previous vi, and the package was named vi. I think there needs to exist a binary named vi in the system, for POSIX compliance, but I am not shure. So if there needs to be a package that provides it, there can't be several packages providing it, or there will be conflicts, and one text editor should not conflict with another. IMHO, naming that package vi only seems natural. AFAIK, there is no such thing as vi nowadays, or is there? Regards.
On Mon, 13 Jul 2009 14:32:45 +0100 Zé Ninguém <meugninez@gmail.com> wrote:
2009/7/13 Magnus Therning <magnus@therning.org>
On Mon, Jul 13, 2009 at 10:18 AM, Ed Jobs<oloringr@gmail.com> wrote:
On Monday 13 July 2009 11:49, solsTiCe d'Hiver wrote:
to the dev: why not rename vi package to nvi ?
+1 to that
Sounds like a good idea, especially since nvi _isn't_ vi in the strictest sense.
Neither was the previous vi, and the package was named vi. I think there needs to exist a binary named vi in the system, for POSIX compliance, but I am not shure. So if there needs to be a package that provides it, there can't be several packages providing it, or there will be conflicts, and one text editor should not conflict with another. IMHO, naming that package vi only seems natural. AFAIK, there is no such thing as vi nowadays, or is there?
Regards.
Isn't it possible to name the things as they are called and simply set up an alias or something when it hurts to type one more letter?
On Mon, Jul 13, 2009 at 9:32 AM, Zé Ninguém<meugninez@gmail.com> wrote:
Neither was the previous vi, and the package was named vi. I think there needs to exist a binary named vi in the system, for POSIX compliance, but I am not shure. So if there needs to be a package that provides it, there can't be several packages providing it, or there will be conflicts, and one text editor should not conflict with another. IMHO, naming that package vi only seems natural. AFAIK, there is no such thing as vi nowadays, or is there?
there needs to be a 'vi' the package does not have to be named vi. as far as package manager conflicts... I'd say just have vi symlink to nvi by default and if people want they can symlink vi to vim or put an alias in there shell config. -- Caleb Cushing http://xenoterracide.blogspot.com
On Monday 13 July 2009 03:49:49 am solsTiCe d'Hiver wrote:
i think you're using [testing] and then use vi-1.79 which is nvi. and not the vi you know which was a stripped down version of vim
nvi behave like the original vi and not like vim. i think there's nothing you can do about this
to the dev: why not rename vi package to nvi ?
I'm using what ever gets started with "vi"; looks like: 00:24 supersff:~> which vi /usr/bin/vi 00:24 supersff:~> l /usr/bin/vi -rwxr-xr-x 3 root root 24684 2009-06-25 01:38 /usr/bin/vi This is weird as hell. Used to be when I typed vi with no arguments, I would get a screen telling me about the version, etc. Now all I get is a blank document. Also, the help in vi (or whatever this is) doesn't even look like the same help I was used to seeing. Now I type :help and get: ~ +=+=+=+=+=+=+=+ To see the list of vi commands, enter ":viusage<CR>" To see the list of ex commands, enter ":exusage<CR>" For an ex command usage statement enter ":exusage [cmd]<CR>" For a vi key usage statement enter ":viusage [key]<CR>" To exit, enter ":q!" Press any key to continue [: to enter more ex commands]: :visuage ^A search forward for cursor word ^B scroll up by screens ^C interrupt an operation (e.g. read, write, search) ^D scroll down by half screens (setting count) ^E scroll down by lines ^F scroll down by screens ^G file status ^H move left by characters ^J move down by lines ^L redraw screen ^M move down by lines (to first non-blank) <snip> What?? Alright, let's try: 00:30 supersff:~> pmq | grep vi <snip> vi 1.81.6-2 <snip> So you are saying, that I used to use VIM and now I am using something call "nvi" that is invoked by typing "vi"? The reason I sound so dense on this is I have always just typed "vi" and gotten the same editor since Mandrake 7.0 (Air). That was what -- in 2000. I am quite fluent in using that editor, just not configuring it. I will search and try and load vim to get the editor back. If the devs really did make the change to vi that gives nvi instead of vim, then it might be worth letting people who want nvi, type "nvi" and letting the rest of us just have "vi" keep working like "vi" has worked for the past ten years. That's not a slap, just seems like if there is the new vi, then it should be invoked with a new command and that the old vi (at least whatever you got when typing vi) should continue to appear after you type vi. I'll go load vim and report back. Thanks! -- David C. Rankin, J.D.,P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 Telephone: (936) 715-9333 Facsimile: (936) 715-9339 www.rankinlawfirm.com
On Saturday 18 July 2009 12:38:29 am David C. Rankin wrote:
On Monday 13 July 2009 03:49:49 am solsTiCe d'Hiver wrote:
i think you're using [testing] and then use vi-1.79 which is nvi. and not the vi you know which was a stripped down version of vim
nvi behave like the original vi and not like vim. i think there's nothing you can do about this
to the dev: why not rename vi package to nvi ?
I'm using what ever gets started with "vi"; looks like:
<snip>
I'll go load vim and report back. Thanks!
WHEW!! All back to normal: 00:45 supersff:~> pms gvim vim vim-a vim-bufexplorer vim-buftabs vim-colorsamplerpack vim-guicolorscheme vim-matchit vim-minibufexpl vim-project vim-workspace Why did the upgrade to testing uninstall vim and install vi anyway? I recall that my /etc/virc was wiped out by one of the 200 packages updated, but I just thought it was the same editor that changed the name of its config file. What was the update that did this so I can avoid it in the future? -- David C. Rankin, J.D.,P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 Telephone: (936) 715-9333 Facsimile: (936) 715-9339 www.rankinlawfirm.com
On Saturday 18 July 2009 12:54:06 am David C. Rankin wrote:
On Saturday 18 July 2009 12:38:29 am David C. Rankin wrote:
On Monday 13 July 2009 03:49:49 am solsTiCe d'Hiver wrote:
i think you're using [testing] and then use vi-1.79 which is nvi. and not the vi you know which was a stripped down version of vim <snip>
I'll go load vim and report back. Thanks!
WHEW!!
All back to normal:
For anyone else caught with the same problem. I wrote a small script that reinstalls vim and moves vi to vi.vni. The script is nothing more that what you would simply do by hand, it just collects all the commands in one place. The script is attached to prevent unwanted line breaks. -- David C. Rankin, J.D.,P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 Telephone: (936) 715-9333 Facsimile: (936) 715-9339 www.rankinlawfirm.com
2009/7/19, David C. Rankin <drankinatty@suddenlinkmail.com>:
For anyone else caught with the same problem. I wrote a small script that reinstalls vim and moves vi to vi.vni. The script is nothing more that what you would simply do by hand, it just collects all the commands in one place. The script is attached to prevent unwanted line breaks.
Your script is not attached. Please, link it to an external website. -- Arch Linux Developer http://www.archlinux.org http://www.archlinux.it
On Sunday 19 July 2009 06:30:45 pm Giovanni Scafora wrote:
2009/7/19, David C. Rankin <drankinatty@suddenlinkmail.com>:
For anyone else caught with the same problem. I wrote a small script that reinstalls vim and moves vi to vi.vni. The script is nothing more that what you would simply do by hand, it just collects all the commands in one place. The script is attached to prevent unwanted line breaks.
Your script is not attached. Please, link it to an external website.
OK, here it is: http://www.3111skyline.com/download/Archlinux/fixes/fixvi -- David C. Rankin, J.D.,P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 Telephone: (936) 715-9333 Facsimile: (936) 715-9339 www.rankinlawfirm.com
David C. Rankin schrieb:
Listmates,
One are where I can use help is vi configuration. With the latest updates to vi and I guess readline, vi behaves very differently than it did just before the update. Specifically, the screen flashes white/black when the cursor is in column 1 if a left cursor is pressed or if vi toggles itself out of input mode.
How can I get rid of the flashing and get rid of vi taking itself out of input/replace mode when it gets to column 1?
The current behavior is better than when I first tried it several weeks ago, but it is still way different from any vi I have used before. Anybody got a handy reference for handling vi changes in the latest version?
Hello, what abot using vim? vi used to be vim and is nvi now. BTW , maybe the developers should consider to use the ex package in AUR rather than nvi. If it is only for having a small editor on the install cd, ex would suit better. Regards Stefan
On Mon, 13 Jul 2009 19:46:50 +0200 Stefan Husmann <stefan-husmann@t-online.de> wrote:
David C. Rankin schrieb:
Listmates,
One are where I can use help is vi configuration. With the latest updates to vi and I guess readline, vi behaves very differently than it did just before the update. Specifically, the screen flashes white/black when the cursor is in column 1 if a left cursor is pressed or if vi toggles itself out of input mode.
How can I get rid of the flashing and get rid of vi taking itself out of input/replace mode when it gets to column 1?
The current behavior is better than when I first tried it several weeks ago, but it is still way different from any vi I have used before. Anybody got a handy reference for handling vi changes in the latest version?
Hello,
what abot using vim?
vi used to be vim and is nvi now.
What Stefan really means here (I think) is "... on Arch"
BTW , maybe the developers should consider to use the ex package in AUR rather than nvi. If it is only for having a small editor on the install cd, ex would suit better.
Regards Stefan
participants (11)
-
Caleb Cushing
-
Daenyth Blank
-
David C. Rankin
-
Dieter Plaetinck
-
Ed Jobs
-
Giovanni Scafora
-
hollunder＠gmx.at
-
Magnus Therning
-
solsTiCe d'Hiver
-
Stefan Husmann
-
Zé Ninguém