From: ShengHuo ZHU <zsh@cs.rochester.edu>
Subject: Re: `v' on a MIME button
Date: Wed, 25 Oct 2000 20:18:06 -0400 [thread overview]
Message-ID: <200010260018.e9Q0I6231860@zsh.2y.net> (raw)
In-Reply-To: <vaf4s21p9d9.fsf@lucy.cs.uni-dortmund.de>
Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann) writes:
> Sometimes I get parts which require strange programs to view. For
> instance, I once got a *.ps.gz which was labeled
> application/octet-stream. Typing `v' on it and then entering "gzcat
> %s | ghostview -" did the trick, of course, but it wasn't easy to
> enter the spaces, since I had to do C-q SPC for them.
>
> I think that this is a sufficiently common operation so that typing
> spaces should be made easier. Thoughts?
Try it now. A SPC is a SPC.
Should another key be bound to minibuffer-complete-word?
ShengHuo
prev parent reply other threads:[~2000-10-26 0:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-10-25 9:18 Kai Großjohann
2000-10-26 0:18 ` ShengHuo ZHU [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200010260018.e9Q0I6231860@zsh.2y.net \
--to=zsh@cs.rochester.edu \
/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).