From: Jean-Christophe Helary <jean.christophe.helary@traduction-libre.org>
To: Eric S Fraga <e.fraga@ucl.ac.uk>
Cc: Help Gnu Emacs mailing list <help-gnu-emacs@gnu.org>
Subject: Re: toc on one side, contents on the other ?
Date: Mon, 8 Jun 2020 23:02:54 +0900 [thread overview]
Message-ID: <4E26C0A7-7510-418F-AC34-72E26403F237@traduction-libre.org> (raw)
In-Reply-To: <87h7vlr8da.fsf@ucl.ac.uk>
> On Jun 8, 2020, at 22:32, Eric S Fraga <e.fraga@ucl.ac.uk> wrote:
>
> On Sunday, 7 Jun 2020 at 13:25, Jean-Christophe Helary wrote:
>> The way windows popup randomly all over the place and the original
>> layout is never restored is a major annoyance in emacs and this
>> package is no exception.
>
> There's never a solution to this problem that would satisfy all
> unfortunately!
>
> My own solution is to have a frame for each different working area so I
> don't have to worry about window arrangements generally. E.g. I have
> one frame for gnus, one or more for agenda (& related), and one each for
> any documents I may be working on (code or org or both).
Thank you Eric.
I've been trying perspectives.el for the last few days. Nice how it "sandboxes" buffers within separate perspectives.
--
Jean-Christophe Helary @brandelune
http://mac4translators.blogspot.com
prev parent reply other threads:[~2020-06-08 14:02 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-06 15:54 toc on one side, contents on the other ? Jean-Christophe Helary
2020-06-06 16:04 ` Drew Adams
2020-06-06 20:34 ` Eric Abrahamsen
2020-06-06 20:42 ` Drew Adams
2020-06-06 21:28 ` Eric Abrahamsen
2020-06-07 4:25 ` Jean-Christophe Helary
2020-06-08 13:32 ` Eric S Fraga
2020-06-08 14:02 ` Jean-Christophe Helary [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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4E26C0A7-7510-418F-AC34-72E26403F237@traduction-libre.org \
--to=jean.christophe.helary@traduction-libre.org \
--cc=e.fraga@ucl.ac.uk \
--cc=help-gnu-emacs@gnu.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).