[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [vile] Is there something special about J[oin], or "why can't I do t

From: Chris G
Subject: Re: [vile] Is there something special about J[oin], or "why can't I do this?"
Date: Tue, 19 Aug 2008 14:52:55 +0100
User-agent: Mutt/1.5.17 (2007-11-01)

On Tue, Aug 19, 2008 at 09:20:26AM -0400, Thomas Dickey wrote:
> On Tue, 19 Aug 2008, Chris G wrote:
>> On Tue, Aug 19, 2008 at 12:26:21PM +0100, Chris G wrote:
>>> I have a file which has a series of CRLF sequences in that I want to
>>> change to a comma followed by a space.
>>> When viewed in vile (as expected) the CRs appear as ^M so it seemed to
>>> me that if I execute (on the command line, i.e. after entering :) the
>>> following:-
>>>     g/
>>> /J
>>> I should get what I want.  However it doesn't work, vile doesn't seem
>>> to accept the J, it just echoes it and then refuses to accept any more
>>> input.  Why isn't J acceptable there and, more to the point, how can I
>>> do what I want to do?
>> Oops, that ^M (a real CR) didn't work very well did it!  :-)
>> The command sequence I'm entering is:-
>>    :g/^M/J
>> where the ^M above is actually entered as ^V^M.
> ...2nd reply (I'm slow).  The 'J' is a key-binding.  vile would be
> looking for a name at that point (and almost all names are lowercase).
> So a lowercase 'j' there would be the abbreviation for join.
Yes, j seems to work, I think some other artefact in the file (or my
stupidity) prevented me from seeing it working the first time I tried it.

Thanks all.

Chris Green

reply via email to

[Prev in Thread] Current Thread [Next in Thread]