From: wmorgan-sup@masanjin.net (William Morgan)
Subject: [sup-talk] new in svn: To/Cc/Bcc prompting and editing (with tab completion)
Date: Sun, 05 Aug 2007 17:12:15 -0700 [thread overview]
Message-ID: <1186358782-sup-8614@south> (raw)
When you compose a new message, Sup will now prompt you for a To:
header. You can also have it prompt you for Cc: and Bcc: by setting
:ask_for_cc and :ask_for_bcc to true in config.yaml.
When editing a message, 'e' will now edit either the message text (via
your editor) or a specific header (via Sup), depending on where the
cursor is. Enter will always edit the message.
Tab completion (on contact aliases, email addresses and full addresses)
is in effect any time you edit a To, From, Cc or Bcc header.
This all really highlights Sup's inability to scroll a text edit field
horizontally. I'll deal with this when I summon up the energy to fight
with Ncurses some more.
--
William <wmorgan-sup at masanjin.net>
reply other threads:[~2007-08-06 0:12 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1186358782-sup-8614@south \
--to=wmorgan-sup@masanjin.net \
/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