From: wirtwolff@gmail.com (Wirt Wolff)
Subject: [sup-talk] Read only mode for sup
Date: Wed, 08 Apr 2009 13:03:07 -0600 [thread overview]
Message-ID: <1239217190-sup-5981@chigamba> (raw)
In-Reply-To: <1239146860-sup-6624@baad>
Excerpts from Ian Smith's message of Tue Apr 07 17:29:04 -0600 2009:
> Excerpts from Nicolas Pouillard's message of Tue Apr 07 14:26:58 -0400 2009:
> > What about adding such a read only mode to sup?
> > * Running a second instance of sup to make searches
> > while we are editing a mail.
>
> This use case already works using buffers - you can switch between them
> fairly easily. I need to rewrite my reflexes still, but I run sup in
> screen, so it can't be that hard.
In my situation buffers aren't enough sometimes. Aside from having to
exit the editor, unless I'm mistaken there's no way to view more than
one buffer at once. Mostly I've appreciated relaxing into that way of
working, and even found it helpful to concentration and productivity.
However, when for example, composing reviews of unapplied patches, each
with one or more discussion threads, I often find myself wishing I could
toggle back and forth between a couple of search buffers and their thread
views in one frame, while composing in another.
There are surely other solutions, hopefully simpler ones, but I've not
gotten motivated enough to work them out yet. A read-only second sup
would get daily usage here. It would be great to not have to switch to
and from "sup mode" while completing tasks referencing multiple threads.
--
regards,
wmw
next prev parent reply other threads:[~2009-04-08 19:03 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-07 18:26 Nicolas Pouillard
2009-04-07 23:29 ` Ian Smith
2009-04-08 8:36 ` Nicolas Pouillard
2009-04-08 12:30 ` Ian Smith
2009-04-08 17:01 ` Andrew Pimlott
2009-04-08 22:18 ` William Morgan
2009-04-08 19:03 ` Wirt Wolff [this message]
2009-04-08 21:49 ` William Morgan
2009-04-09 11:55 ` Nicolas Pouillard
2009-04-09 17:30 ` William Morgan
2009-04-10 8:36 ` Nicolas Pouillard
2009-04-10 12:24 ` William Morgan
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=1239217190-sup-5981@chigamba \
--to=wirtwolff@gmail.com \
/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