On Sun, 26 Aug 2012 08:26:48 Markus Falb wrote:
> On 20.8.2012 19:16, Gordon Messmer wrote:
> > On 08/20/2012 04:07 AM, Joerg Schilling wrote:
> >> Gordon Messmer wrote:
> >>
> Actually, it's a shell alias. And then, only if "vim" is installed,
> which it isn't in some configurations.
On 20.8.2012 19:16, Gordon Messmer wrote:
> On 08/20/2012 04:07 AM, Joerg Schilling wrote:
>> Gordon Messmer 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 i
On 08/20/2012 04:07 AM, Joerg Schilling wrote:
> Gordon Messmer 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 symlink no
On Mon, Aug 20, 2012 at 10:43 AM, Joerg Schilling
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 started this thread turns out
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 source,
Joerg Schilling wrote:
> 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 T
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 nineties? or we
Joerg Schilling wrote:
> William Hooper wrote:
>> On Mon, Aug 20, 2012 at 7:19 AM, Joerg Schilling
>> wrote:
>> > Reindl Harald 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
Reindl Harald 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
--
EMail:jo...@schily.isdn.cs.tu-berlin.de (
William Hooper wrote:
> On Mon, Aug 20, 2012 at 7:19 AM, Joerg Schilling
> wrote:
> >
> > Reindl Harald 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 t
On Mon, Aug 20, 2012 at 7:19 AM, Joerg Schilling
wrote:
>
> Reindl Harald 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 there is a program called "vi" and another
> pr
Reindl Harald wrote:
>
>
> Am 20.08.2012 13:07, schrieb Joerg Schilling:
> > Gordon Messmer 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 i
Gordon Messmer 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 server install
On Sun, Aug 19, 2012 at 2:31 AM, Gordon Messmer 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
> b
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.
* Les Mikesell [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 bizarre behavior, prefe
On Fri, 2012-08-17 at 11:02 -0500, Les Mikesell wrote:
> On Fri, Aug 17, 2012 at 10:35 AM, John Doe 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 line
On Fri, Aug 17, 2012 at 10:35 AM, John Doe 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
> On Fri, Aug 17, 2012 at 5:22 AM, John Doe wrote:
>> From: Les Mikesell
>>
>>> 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 add
On Fri, Aug 17, 2012 at 5:22 AM, John Doe wrote:
> From: Les Mikesell
>
>> 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
From: Les Mikesell
> 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
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:
>
+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 autoindent specified twice - once
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:
> /usr/share
Les Mikesell wrote:
> On Thu, Aug 16, 2012 at 1:44 PM, 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
On Thu, Aug 16, 2012 at 1:44 PM, 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 biza
> From: Les Mikesell
> To: CentOS mailing list
> 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 ad
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
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 biz
29 matches
Mail list logo
