all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Mattias Engdegård" <mattiase@acm.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 49624@debbugs.gnu.org, monnier@iro.umontreal.ca, juri@linkov.net
Subject: bug#49624: compilation message end-column function off-by-one bug
Date: Mon, 19 Jul 2021 12:39:59 +0200	[thread overview]
Message-ID: <5FDA92A6-421D-4A91-A2D9-D0101B115037@acm.org> (raw)
In-Reply-To: <83czrf773k.fsf@gnu.org>

18 juli 2021 kl. 21.30 skrev Eli Zaretskii <eliz@gnu.org>:

> ??? Why not?

Not sure what you mean (and I don't really think it's something we disagree about) but in any case it's beside the point. Emacs should behave as expected by the user, as documented, and in a consistent way. Currently it does neither.

The more I think about it, the clearer it becomes that it's a plain bug which I'm making too much fuss about and should just go ahead and fix the stupid thing. It was mainly reported on the unlikely chance that Juri and/or Stefan would remember something interesting about the code, but that's secondary.






  reply	other threads:[~2021-07-19 10:39 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-18 19:00 bug#49624: compilation message end-column function off-by-one bug Mattias Engdegård
2021-07-18 19:10 ` Eli Zaretskii
2021-07-18 19:13   ` Mattias Engdegård
2021-07-18 19:30     ` Eli Zaretskii
2021-07-19 10:39       ` Mattias Engdegård [this message]
     [not found]         ` <875yx6qtwg.fsf@mail.linkov.net>
     [not found]           ` <5BAAD7D4-A578-4DB5-925E-ECE02B4F4B56@acm.org>
     [not found]             ` <87pmvevv28.fsf@mail.linkov.net>
2021-07-23 13:24               ` Mattias Engdegård
2021-07-26 17:06                 ` Juri Linkov
2021-07-26 19:30                   ` Mattias Engdegård

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=5FDA92A6-421D-4A91-A2D9-D0101B115037@acm.org \
    --to=mattiase@acm.org \
    --cc=49624@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    --cc=juri@linkov.net \
    --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.