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
On Mon, Jul 13, 2009 at 8:00 AM, David C.
Rankindrankina...@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
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.
On Mon, Jul 13, 2009 at 10:18 AM, Ed Jobsolori...@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
2009/7/13 Magnus Therning mag...@therning.org
On Mon, Jul 13, 2009 at 10:18 AM, Ed Jobsolori...@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
On Mon, Jul 13, 2009 at 05:32, Magnus Therningmag...@therning.org wrote:
On Mon, Jul 13, 2009 at 10:18 AM, Ed Jobsolori...@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
On Tue-2009/07/07-22:17 clemens fischer wrote:
(gdb) bt
incomplete CFI data; unspecified registers (e.g., eax) at 0xb7fa838a...#0
0xb7fa84dc in _getopt_internal_r ()
from /lib/libc.so.6
#1 0xb7fa946e in _getopt_internal () from /lib/libc.so.6
#2 0xb7fa96b9 in getopt_long () from
On Mon, 13 Jul 2009 14:32:45 +0100
Zé Ninguém meugni...@gmail.com wrote:
2009/7/13 Magnus Therning mag...@therning.org
On Mon, Jul 13, 2009 at 10:18 AM, Ed Jobsolori...@gmail.com wrote:
On Monday 13 July 2009 11:49, solsTiCe d'Hiver wrote:
to the dev:
why not rename vi package to
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
On Mon, 13 Jul 2009 19:46:50 +0200
Stefan Husmann stefan-husm...@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
On Mon, Jul 13, 2009 at 9:32 AM, Zé Ninguémmeugni...@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
On Fri, Jul 10, 2009 at 11:00:00AM +0200, Thomas Bächler wrote:
New upstream release, please test and sign off. I also remove the ABI
version 1 ucode, which should not be needed anymore with recent kernels.
I can still connect to my router using wpa and netcfg.
The other day I tried to install K3B on my x86_64 laptop, and midway
through it I got some errors, so I ran pacman -Sy k3b and it got about
midway through before I started getting error messages about the
computer not being able to find libreadline.so. I use zsh as my shell
for my normal user, but
Samuel Baldwin wrote:
-s), but now when I boot I get errors when it tries to enter runlevel
3 (I haven't played with any runlevel stuff):
/bin/bash: error while loading shared libraries: libreadline.so.5:
cannot open shared object file: No such file or directory
INIT: Entering runlvel: 3
Yup! Works great, thank you!
--
Samuel 'Shardz' Baldwin - staticfree.info/~samuel
16 matches
Mail list logo
