From: Stefan Monnier via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Eshel Yaron <me@eshelyaron.com>, 62453@debbugs.gnu.org
Subject: bug#62453: 30.0.50; Semicolon in view-lossage yields wrong alignment
Date: Sun, 26 Mar 2023 11:11:06 -0400 [thread overview]
Message-ID: <jwvedpb7doq.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <83wn33ams3.fsf@gnu.org> (Eli Zaretskii's message of "Sun, 26 Mar 2023 12:23:56 +0300")
> Stefan, any better ideas? It looks like relying on comment-indent is
> quite fragile here,
Agreed.
> as keys can include a semi-colon, which will be
> interpreted as beginning a comment in too many places. I wonder
> whether the two extra bindings I add below really plug all the holes.
Here's another problem:
C-x 5 2 ;; make-frame-command
;; handle-switch-frame
<help-echo> <help-echo> ;; handle-switch-frame
;; handle-switch-frame
;; handle-switch-frame
;; handle-switch-frame
;; handle-switch-frame
;; handle-switch-frame
;; handle-switch-frame
C- ; ;; nil
; ;; self-insert-command
C-h l ;; view-lossage
I'm not sure why there's no `switch-frame` event but it absence leads to
incorrectly indenting the `;; handle-switch-frame`.
We're probably better off indenting "by hand".
Stefan
next prev parent reply other threads:[~2023-03-26 15:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-26 5:33 bug#62453: 30.0.50; Semicolon in view-lossage yields wrong alignment Eshel Yaron via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-03-26 9:23 ` Eli Zaretskii
2023-03-26 9:39 ` Eshel Yaron via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-03-26 15:11 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2023-03-26 15:27 ` Eli Zaretskii
2023-03-27 7:00 ` Juri Linkov
2023-03-29 11:58 ` Eli Zaretskii
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=jwvedpb7doq.fsf-monnier+emacs@gnu.org \
--to=bug-gnu-emacs@gnu.org \
--cc=62453@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=me@eshelyaron.com \
--cc=monnier@iro.umontreal.ca \
/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.