On 20.8.2012 19:16, Gordon Messmer wrote:
On 08/20/2012 04:07 AM, Joerg Schilling wrote:
Gordon Messmeryiny...@eburg.com wrote:
Actually, it's a shell alias. And then, only if vim is installed,
which it isn't in some configurations. IIRC, desktop systems have him
by default, but server
On Sun, 26 Aug 2012 08:26:48 Markus Falb markus.f...@fasel.at wrote:
On 20.8.2012 19:16, Gordon Messmer wrote:
On 08/20/2012 04:07 AM, Joerg Schilling wrote:
Gordon Messmeryiny...@eburg.com wrote:
Actually, it's a shell alias. And then, only if vim is installed,
which it isn't in
Gordon Messmer yiny...@eburg.com wrote:
On 08/16/2012 04:55 PM, SilverTip257 wrote:
vi is generally a symlink to vim these days.
Actually, it's a shell alias. And then, only if vim is installed,
which it isn't in some configurations. IIRC, desktop systems have him
by default, but
Reindl Harald h.rei...@thelounge.net wrote:
Am 20.08.2012 13:07, schrieb Joerg Schilling:
Gordon Messmer yiny...@eburg.com wrote:
On 08/16/2012 04:55 PM, SilverTip257 wrote:
vi is generally a symlink to vim these days.
Actually, it's a shell alias. And then, only if vim is
On Mon, Aug 20, 2012 at 7:19 AM, Joerg Schilling
joerg.schill...@fokus.fraunhofer.de wrote:
Reindl Harald h.rei...@thelounge.net wrote:
you are aware that you are posting to the CENTOS-list?
Of course
the topic is about vi default in CENTOS 6.x so what
You seem to missunderstand that
William Hooper whooper...@gmail.com wrote:
On Mon, Aug 20, 2012 at 7:19 AM, Joerg Schilling
joerg.schill...@fokus.fraunhofer.de wrote:
Reindl Harald h.rei...@thelounge.net wrote:
you are aware that you are posting to the CENTOS-list?
Of course
the topic is about vi default in
Reindl Harald h.rei...@thelounge.net wrote:
This just verifies that you don't have a vi
boah how often should we explain it until you
understand taht on CENTOS there is NO vi package
there is only VIM
Nice to see, that you finally realized it too.
Jörg
--
Joerg Schilling wrote:
William Hooper whooper...@gmail.com wrote:
On Mon, Aug 20, 2012 at 7:19 AM, Joerg Schilling
joerg.schill...@fokus.fraunhofer.de wrote:
Reindl Harald h.rei...@thelounge.net wrote:
you are aware that you are posting to the CENTOS-list?
Of course
the topic is
m.r...@5-cent.us wrote:
This just verifies that you're playing word games. If you want vi that's
not vim, may I ask which *version* of vi you would consider to be vi - one
from, say, Sun OS 3? Or from the Irix that ran on our Indigo in the
early/mid-nineties? or one from Tru-64 in the late
Joerg Schilling wrote:
m.r...@5-cent.us wrote:
This just verifies that you're playing word games. If you want vi that's
not vim, may I ask which *version* of vi you would consider to be vi -
one
from, say, Sun OS 3? Or from the Irix that ran on our Indigo in the
early/mid-nineties? or one
m.r...@5-cent.us wrote:
You currently may have the vi source from aprox. 1979 under a 4 clause BSD
license or the current Solaris vi under the CDDL. The latter was POSIX
compliant approved.
And so you assert that if you don't have a version of vi that is strictly
compatible with the 1979
On Mon, Aug 20, 2012 at 10:43 AM, Joerg Schilling
joerg.schill...@fokus.fraunhofer.de wrote:
People who use the vi however complained that vim is not fully vi compatible
and
that they prefer to have a real vi under the name vi. People who prefer vim
could still call vim.
My complaint that
On 08/20/2012 04:07 AM, Joerg Schilling wrote:
Gordon Messmeryiny...@eburg.com wrote:
Actually, it's a shell alias. And then, only if vim is installed,
which it isn't in some configurations. IIRC, desktop systems have him
by default, but server installations do not.
It is neither a
On 08/16/2012 04:55 PM, SilverTip257 wrote:
vi is generally a symlink to vim these days.
Actually, it's a shell alias. And then, only if vim is installed,
which it isn't in some configurations. IIRC, desktop systems have him
by default, but server installations do not.
On Sun, Aug 19, 2012 at 2:31 AM, Gordon Messmer yiny...@eburg.com wrote:
On 08/16/2012 04:55 PM, SilverTip257 wrote:
vi is generally a symlink to vim these days.
Actually, it's a shell alias. And then, only if vim is installed,
which it isn't in some configurations. IIRC, desktop systems
* Les Mikesell lesmikes...@gmail.com [08/16/2012 14:23]:
When I use copy/paste text into a window running vi, if there is a
single line starting with '#', in the pasted content, it adds a # to
all subsequent lines and indents each an additional level. Is there
some way to eliminate this
From: Les Mikesell lesmikes...@gmail.com
When I use copy/paste text into a window running vi, if there is a
single line starting with '#', in the pasted content, it adds a # to
all subsequent lines and indents each an additional level. Is there
some way to eliminate this bizarre behavior,
On Fri, Aug 17, 2012 at 5:22 AM, John Doe jd...@yahoo.com wrote:
From: Les Mikesell lesmikes...@gmail.com
When I use copy/paste text into a window running vi, if there is a
single line starting with '#', in the pasted content, it adds a # to
all subsequent lines and indents each an additional
From: Les Mikesell lesmikes...@gmail.com
On Fri, Aug 17, 2012 at 5:22 AM, John Doe jd...@yahoo.com wrote:
From: Les Mikesell lesmikes...@gmail.com
When I use copy/paste text into a window running vi, if there is a
single line starting with '#', in the pasted content, it adds a
# to
On Fri, Aug 17, 2012 at 10:35 AM, John Doe jd...@yahoo.com wrote:
When I use copy/paste text into a window running vi, if there is a
single line starting with '#', in the pasted content, it adds a
# to
all subsequent lines and indents each an additional level. Is there
some way to
On Fri, 2012-08-17 at 11:02 -0500, Les Mikesell wrote:
On Fri, Aug 17, 2012 at 10:35 AM, John Doe jd...@yahoo.com wrote:
When I use copy/paste text into a window running vi, if there is a
single line starting with '#', in the pasted content, it adds a
# to
all subsequent lines and
When I use copy/paste text into a window running vi, if there is a
single line starting with '#', in the pasted content, it adds a # to
all subsequent lines and indents each an additional level. Is there
some way to eliminate this bizarre behavior, preferably globally and
permanently so I don't
On Thu, 16 Aug 2012 13:23:28 -0500
Les Mikesell wrote:
When I use copy/paste text into a window running vi, if there is a
single line starting with '#', in the pasted content, it adds a # to
all subsequent lines and indents each an additional level. Is there
some way to eliminate this
Frank Cox wrote:
On Thu, 16 Aug 2012 13:23:28 -0500
Les Mikesell wrote:
When I use copy/paste text into a window running vi, if there is a
single line starting with '#', in the pasted content, it adds a # to
all subsequent lines and indents each an additional level. Is there
some way to
From: Les Mikesell lesmikes...@gmail.com
To: CentOS mailing list centos@centos.org
Sent: Thursday, August 16, 2012 11:23 AM
Subject: [CentOS] vi defaults in 6.x
When I use copy/paste text into a window running vi, if there is a
single line starting
On Thu, Aug 16, 2012 at 1:44 PM, m.r...@5-cent.us wrote:
When I use copy/paste text into a window running vi, if there is a
single line starting with '#', in the pasted content, it adds a # to
all subsequent lines and indents each an additional level. Is there
some way to eliminate this
Les Mikesell wrote:
On Thu, Aug 16, 2012 at 1:44 PM, m.r...@5-cent.us wrote:
When I use copy/paste text into a window running vi, if there is a
single line starting with '#', in the pasted content, it adds a # to
all subsequent lines and indents each an additional level. Is there
some way
On Thu, 16 Aug 2012, Les Mikesell wrote:
It is probably trying to be smarter than we are and doing something
context-sensitive. Try naming the file you are editing something.pl.
That is exactly what it isdoing.
A .pl file will probably syntaxted as a perl script.
From man vim:
list centos@centos.org
Sent: Thursday, August 16, 2012 11:23 AM
Subject: [CentOS] vi defaults in 6.x
When I use copy/paste text into a window running vi, if there is a
single line starting with '#', in the pasted content, it adds a # to
all subsequent lines and indents each an additional level
SilverTip257 wrote:
+1 for .vimrc config files
vi is generally a symlink to vim these days.
@Les,
I've seen the auto-comment behavior you speak of. You may want to set
formatoptions [0] in your .vimrc
[0] http://vimdoc.sourceforge.net/htmldoc/change.html#fo-table
@Joseph:
You have
30 matches
Mail list logo
