From: Jean-Christophe Helary <jean.christophe.helary@traduction-libre.org>
To: Eric Abrahamsen <eric@ericabrahamsen.net>
Cc: Help Gnu Emacs mailing list <help-gnu-emacs@gnu.org>
Subject: Re: toc on one side, contents on the other ?
Date: Sun, 7 Jun 2020 13:25:39 +0900 [thread overview]
Message-ID: <03495B67-5C01-4E30-AD52-3B863D40C68C@traduction-libre.org> (raw)
In-Reply-To: <87a71grl05.fsf@ericabrahamsen.net>
> On Jun 7, 2020, at 5:34, Eric Abrahamsen <eric@ericabrahamsen.net> wrote:
>
> Drew Adams <drew.adams@oracle.com> writes:
>
>>> I'm trying to keep an org file TOC in one window and send narrowed buffers to
>>> another window, but I can't seem to find how to do that with vanilla
>>> org/emacs.
>>
>> Maybe `narrow-indirect.el' will help - dunno.
>>
>> https://www.emacswiki.org/emacs/NarrowIndirect
>>
>> You may also need to fiddle with `display-buffer-alist'
>> or whatever, to get buffers shown where you want them - dunno.
>
> Or the org-toc package seems to do this, or almost this. I don't know
> if it counts as "vanilla", but it's part of the org-plus-contrib
> package.
Thank you. I tried it. It was basically what I was looking for.
But, (rant) I just don't like the liberties developers take with the windows layout, which may be based *in part* on the emacs infrastructure.
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.
> It doesn't seem to do a narrowing thing by default, but I'll bet it
> wouldn't be hard to add.
But it refers to the correct header, so that's good enough.
--
Jean-Christophe Helary @brandelune
http://mac4translators.blogspot.com
next prev parent reply other threads:[~2020-06-07 4:25 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 [this message]
2020-06-08 13:32 ` Eric S Fraga
2020-06-08 14:02 ` Jean-Christophe Helary
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=03495B67-5C01-4E30-AD52-3B863D40C68C@traduction-libre.org \
--to=jean.christophe.helary@traduction-libre.org \
--cc=eric@ericabrahamsen.net \
--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).