From: Hamish <dmishd@gmail.com>
To: sup-devel <sup-devel@rubyforge.org>
Subject: [sup-devel] editing messages outside of sup
Date: Sun, 20 Feb 2011 22:02:54 +0000 [thread overview]
Message-ID: <1298239068-sup-6985@whisper> (raw)
Hello
It is often useful to be able to look at messages while writing a message.
While I can exit my editor and look at other messages, and then come back to
my editor, it would be nice to have both open at the same time. So I've
written some code that allows you to do that. When you are in
compose-mode/reply-mode/etc you can press 'E' and it will transform into
a buffer showing a file path of the file to edit, and a key to press ('E'
again) to say you've finished.
So you can open the file in another editor, whether on your desktop, in
another terminal, in a screen session split so you can see both, or whatever.
While editing you can still navigate around sup's buffers and copy text,
email addresses etc into your editor and so on.
Then when you're done, you can exit the editor, navigate back to the edit
buffer and press 'E' to go back to normal edit-message-mode and carry on as
normal.
As part of this, I've created a way to hide the original buffer. I think
I handle buffer killing properly in the various states (file still being
edited, file saved etc), but someone will doubtless find an edge case
...
For the moment this work is in the async_message_edit branch. If no one
shouts about this being a terrible idea then I'll merge it into next
within a week.
Hamish Downer
_______________________________________________
Sup-devel mailing list
Sup-devel@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-devel
next reply other threads:[~2011-02-20 22:03 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-20 22:02 Hamish [this message]
2011-02-26 19:23 ` Hamish
2011-02-27 1:15 ` Alvaro Herrera
2011-02-27 2:51 ` Roni Choudhury
2011-02-27 15:31 ` Ico Doornekamp
2011-02-27 17:20 ` Hamish
2011-02-27 19:44 ` Ico Doornekamp
2011-04-04 23:01 ` Hamish
2011-04-05 4:38 ` Ico Doornekamp
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=1298239068-sup-6985@whisper \
--to=dmishd@gmail.com \
--cc=sup-devel@rubyforge.org \
/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