From: andrew@pimlott.net (Andrew Pimlott)
Subject: [sup-talk] Odd key bug
Date: Mon, 27 Jul 2009 13:11:53 -0700 [thread overview]
Message-ID: <20090727201153.GI14010@pimlott.net> (raw)
In-Reply-To: <1248720085-sup-7444@valgus>
On Mon, Jul 27, 2009 at 09:47:00PM +0300, Tarko Tikan wrote:
> Currently, as the external editor is run, there is no way to switch between sup and external editor (for obvious reasons). Is anyone aware of any better idea how to integrate vim (even better, any editor) into sup and still have the excellent buffer system.
My idea is to make sup act like a shell and implement job control, so
when you ctrl-z out of your editor, you're back in sup. You can have
multiple editors stopped in the background, and resume any of them at
any point.
Andrew
prev parent reply other threads:[~2009-07-27 20:11 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-27 17:13 Edward Z. Yang
2009-07-27 17:27 ` Alex Vandiver
2009-07-27 17:52 ` Ben Walton
2009-07-27 17:33 ` William Morgan
2009-07-27 18:13 ` Edward Z. Yang
2009-07-27 18:30 ` Edward Z. Yang
2009-07-27 19:15 ` Edward Z. Yang
2009-07-28 15:17 ` William Morgan
2009-07-28 15:31 ` Ben Walton
2009-07-27 18:47 ` Tarko Tikan
2009-07-27 20:11 ` Andrew Pimlott [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=20090727201153.GI14010@pimlott.net \
--to=andrew@pimlott.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