From: Michael Welsh Duggan <md5i@cs.cmu.edu>
Subject: Re: For lack of content...
Date: Tue, 01 Sep 1998 14:30:24 GMT [thread overview]
Message-ID: <v1tsoib7vnm.fsf@peoria.mt.cs.cmu.edu> (raw)
In-Reply-To: <m3emtwx2oi.fsf@sparky.gnus.org>
Lars Magne Ingebrigtsen <larsi@gnus.org> writes:
> Michael Welsh Duggan <md5i@cs.cmu.edu> writes:
>
> > 2) A washing method, for which the user can supply a coding-system
> > with which to decode the article.
>
> And this.
I tried it out today. Very nice! Only one minor complaint, and not
necessarily one you should "fix". When using `C-u M W c', it would be
nice to have tab completion on the entire set of coding systems (as
per (interactive "z")) instead of the small subset. (I am much more
used to typing old-jis than iso-whatever.) Typing old-jis works, I am
just used to the tab completion. I won't complain if you don't change
it however, as the smaller list of matches may well be worth it.
--
Michael Duggan
(md5i@cs.cmu.edu)
.
next prev parent reply other threads:[~1998-09-01 14:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-08-31 18:18 Michael Welsh Duggan
1998-08-31 21:27 ` Lars Magne Ingebrigtsen
1998-08-31 22:02 ` Michael Welsh Duggan
1998-09-01 1:47 ` Justin Sheehy
1998-09-01 14:30 ` Michael Welsh Duggan [this message]
1998-09-01 22:33 ` Lars Magne Ingebrigtsen
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=v1tsoib7vnm.fsf@peoria.mt.cs.cmu.edu \
--to=md5i@cs.cmu.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).