unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann)
Subject: Re: Define colon commands in viper?
Date: Wed, 04 Sep 2002 19:18:14 +0200	[thread overview]
Message-ID: <vaf4rd5u10p.fsf@lucy.cs.uni-dortmund.de> (raw)
In-Reply-To: 87n0qzt2bs.fsf@stewart.floobin.cx

Edward O'Connor <ted@stewart.floobin.cx> writes:

>> How do I define a colon command in viper, such that `:meep' calls
>> the `ding' function, say?
>
> There's probably a better way to do this, but here's what I do in my
> .emacs file WRT :open and the like:

You pointed me in the right direction.  I guess that it would work to
add an entry to ex-token-alist.  Thanks!

kai
-- 
A large number of young women don't trust men with beards.  (BFBS Radio)

      reply	other threads:[~2002-09-04 17:18 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-03 22:25 Define colon commands in viper? Kai Großjohann
2002-09-04  8:53 ` Edward O'Connor
2002-09-04 17:18   ` Kai Großjohann [this message]

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

  List information: https://www.gnu.org/software/emacs/

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

  git send-email \
    --in-reply-to=vaf4rd5u10p.fsf@lucy.cs.uni-dortmund.de \
    --to=kai.grossjohann@cs.uni-dortmund.de \
    /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 read-only IMAP folder(s) and NNTP newsgroup(s).