The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: ralph@inputplus.co.uk (Ralph Corderoy)
Subject: [TUHS] basic tools / Universal Unix
Date: Mon, 30 Oct 2017 14:05:28 +0000	[thread overview]
Message-ID: <20171030140528.42DB1218A6@orac.inputplus.co.uk> (raw)
In-Reply-To: <20171030025444.16E04156E7D8@mail.bitblocks.com>

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 818 bytes --]

Hi Bakul,

> Thanks, didn't know about q.  However, nvi doesn't have q.

It's just a means of recording typing into a register.  Exactly the same
can be achieved by typing into the buffer and then yanking into the
named register, being careful to leave off the LF at the end of the line
if it's not wanted, e.g. «"qy$».

> What I was getting at is being able to define commands that can take
> one or two arguments like the bulitins, separate from any key mapping.

If `3wy' yanked three words then the macro in register `q' could start
with `y' allowing `3w at q' to pass a region to the macro, but it doesn't.
:-)  I think one's left with setting a mark, or using automatic ones set
at various times by vim, and the macro using those to know its region.

-- 
Cheers, Ralph.
https://plus.google.com/+RalphCorderoy


  reply	other threads:[~2017-10-30 14:05 UTC|newest]

Thread overview: 61+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-16 17:52 Clem Cole
2017-10-16 18:16 ` Tom Ivar Helbekkmo
2017-10-16 20:39   ` Toby Thain
2017-10-16 18:54 ` [TUHS] " Dan Cross
2017-10-17 13:51   ` Tony Finch
2017-10-17 20:22     ` Steffen Nurpmeso
2017-10-16 20:05 ` Bakul Shah
2017-10-30  0:55   ` Ralph Corderoy
2017-10-30  2:54     ` Bakul Shah
2017-10-30 14:05       ` Ralph Corderoy [this message]
2017-10-16 20:39 ` Andy Kosela
2017-10-18 23:03 Doug McIlroy
2017-10-19  3:53 ` Random832
2017-10-19 14:33   ` Steffen Nurpmeso
2017-10-19 14:41     ` Random832
2017-10-19 21:03       ` Steffen Nurpmeso
2017-10-20 19:54       ` Steffen Nurpmeso
2017-10-19 14:32 ` Steffen Nurpmeso
2017-10-30 14:16 Noel Chiappa
2017-10-30 14:40 ` Clem Cole
2017-10-30 15:23 ` Arthur Krewat
2017-10-30 20:56 ` Dave Horsfall
2017-10-31 10:50   ` Ronald Natalie
2017-11-01  3:23     ` Dave Horsfall
2017-11-01 13:25       ` Tim Bradshaw
2017-11-16  1:17         ` Dario Niedermann
2017-11-15  1:25       ` Nemo
2017-11-15  2:10         ` Will Senn
2017-11-15  2:16           ` Larry McVoy
2017-11-15  2:37             ` Warner Losh
2017-11-15  3:07               ` Will Senn
2017-11-15 16:13                 ` Arthur Krewat
2017-11-15 16:23                   ` Arthur Krewat
2017-11-15 16:48                     ` Clem Cole
2017-11-15 18:13                       ` Bakul Shah
2017-11-15 19:01                         ` Clem Cole
2017-11-15  9:58               ` Andy Kosela
2017-11-15 11:42           ` Ralph Corderoy
2017-11-01 14:05     ` Ralph Corderoy
2017-11-01 16:42       ` arnold
2017-11-01 17:17         ` Ralph Corderoy
2017-11-01 18:03           ` Dan Cross
2017-11-01 18:06           ` arnold
2017-11-01 20:16             ` Bakul Shah
2017-11-01 20:37               ` arnold
2017-11-01 21:04                 ` Bakul Shah
2017-11-02  0:05                 ` Chet Ramey
2017-11-02  0:10             ` Ralph Corderoy
2017-10-31 16:43   ` Don Hopkins
2017-11-02 17:48   ` Paul Winalski
2017-10-30 21:50 ` Charles Anthony
2017-10-30 21:40 Noel Chiappa
2017-10-31 19:23 Norman Wilson
2017-11-01 22:51 Norman Wilson
2017-11-01 23:09 ` Lyndon Nerenberg
2017-11-02 20:29 ` Grant Taylor
2017-11-15 14:06 Noel Chiappa
2017-11-15 17:12 ` Ralph Corderoy
2017-11-15 17:47   ` Larry McVoy
2017-11-15 18:40   ` Bakul Shah
2017-11-15 19:58     ` Larry McVoy

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20171030140528.42DB1218A6@orac.inputplus.co.uk \
    --to=ralph@inputplus.co.uk \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).