From: Jim Porter <jporterbugs@gmail.com>
To: Juri Linkov <juri@linkov.net>
Cc: 71284@debbugs.gnu.org
Subject: bug#71284: 30.0.50; [PATCH] Add support for outline-minor-mode to Eshell
Date: Wed, 5 Jun 2024 18:52:15 -0700 [thread overview]
Message-ID: <28afde26-8d83-8b5f-b617-a2797ea5e1fc@gmail.com> (raw)
In-Reply-To: <86o78i4j8u.fsf@mail.linkov.net>
On 6/2/2024 11:45 PM, Juri Linkov wrote:
>> In any case, the more I think about this, the more my current patch seems
>> like the wrong way to go about this. Even just describing the user-facing
>> behavior in all scenarios is pretty complex, so I think it might be better
>> to keep it simple and have a single outline level.
>>
>> That said, for the multi-line prompt case, I wonder if it would make sense
>> for outline.el to support multi-line headers. If I could mark the entire
>> prompt + command input as a "header", then collapsing it would look better:
>> users would still see all of their input in the collapsed node.
>
> The multi-line headers have such disadvantage that the outlines
> are not compact anymore. Also multi-line headers might have
> more technial issues with displaying an ellipsis at the end.
Given that you mentioned a few other cases where multi-line headers
might be nice (assuming the number of lines is small), maybe it would
make sense to see what an implementation of that looks like. I'll see
about writing a patch for this.
(Another interesting thing I might try is to see if we could provide
some custom single-line abbreviation for multi-line headers. That would
let us have compact headers when they're collapsed, even if the "header"
part is really multiple lines when expanded.)
next prev parent reply other threads:[~2024-06-06 1:52 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-31 5:18 bug#71284: 30.0.50; [PATCH] Add support for outline-minor-mode to Eshell Jim Porter
2024-05-31 6:05 ` Eli Zaretskii
2024-05-31 19:33 ` Jim Porter
2024-06-01 5:58 ` Eli Zaretskii
2024-05-31 6:51 ` Juri Linkov
2024-05-31 20:02 ` Jim Porter
2024-06-02 6:37 ` Juri Linkov
2024-06-03 4:34 ` Jim Porter
2024-06-03 6:45 ` Juri Linkov
2024-06-06 1:52 ` Jim Porter [this message]
2024-06-06 6:19 ` Juri Linkov
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=28afde26-8d83-8b5f-b617-a2797ea5e1fc@gmail.com \
--to=jporterbugs@gmail.com \
--cc=71284@debbugs.gnu.org \
--cc=juri@linkov.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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.