From: lucio@proxima.alt.za
To: 9fans@cse.psu.edu
Subject: [9fans] silly suggestions
Date: Thu, 31 Mar 2005 06:34:51 +0200 [thread overview]
Message-ID: <cdf35443431d54c4d5313e257b383115@proxima.alt.za> (raw)
Anyone want to beat me to the implementation of the following, or
point out why they should not be implemented?
1. Use "#" rather than "_" in the renaming of files by "replica" so
that one can clean up without regard for legitimate files starting in
an underscore.
2. Change Mail so that (a) the vertical bar is followed immediately
by the "fmt" command, saving a little tag line real estate (yes, it
does work) in the "mail" windows and (b) the "Undo" command is a
little more common in "Mail" taglines than is presently the case.
3. (I won't get to this in any hurry) Teach ACME Mail (a) to use
templates for new messages and (b) to "group" quote.
++L
next reply other threads:[~2005-03-31 4:34 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-31 4:34 lucio [this message]
2005-03-31 5:21 ` geoff
2005-03-31 7:02 ` boyd, rounin
2005-03-31 7:16 ` geoff
2005-04-01 4:06 ` lucio
2005-04-01 12:22 ` Russ Cox
2005-03-31 11:57 ` Russ Cox
2005-03-31 17:13 ` Heiko Dudzus
2005-03-31 17:15 ` Russ Cox
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=cdf35443431d54c4d5313e257b383115@proxima.alt.za \
--to=lucio@proxima.alt.za \
--cc=9fans@cse.psu.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).