all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Stefan Kangas <stefankangas@gmail.com>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 57883-done@debbugs.gnu.org, JD Smith <jdtsmith@gmail.com>
Subject: bug#57883: compilation-get-file-structure mishandles buffers
Date: Sun, 3 Sep 2023 02:18:03 -0700	[thread overview]
Message-ID: <CADwFkmk+ynNCm1BY-nTZyXtCK0Pf2Rh4JPDBd41VSJ=V=B4tJQ@mail.gmail.com> (raw)
In-Reply-To: <87edw93qa6.fsf@gnus.org> (Lars Ingebrigtsen's message of "Sun, 18 Sep 2022 12:55:45 +0200")

Lars Ingebrigtsen <larsi@gnus.org> writes:

> JD Smith <jdtsmith@gmail.com> writes:
>
>> Note that this is useful for modes which report errors in text from open buffers, which
>> may have no associated file.   The issue is this line in `compilation-get-file-structure’:
>>
>> (if (file-name-absolute-p filename)
>>    (setq filename (concat comint-file-name-prefix filename)))
>> which signals an
>
> This is how your email ended, so I think your message may have been cut
> off?
>
> In any case, do you have a recipe to reproduce the problem, starting
> from "emacs -Q"?

More information was requested, but none was given within 12 months, so
I'm closing this bug.

If this is still an issue, please reply to this email (use "Reply to
all" in your email client) and we can reopen the bug report.





  reply	other threads:[~2023-09-03  9:18 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-17 14:25 bug#57883: compilation-get-file-structure mishandles buffers JD Smith
2022-09-18 10:55 ` Lars Ingebrigtsen
2023-09-03  9:18   ` Stefan Kangas [this message]
2023-09-03 13:36     ` JD Smith
2023-09-03 18:27       ` Stefan Kangas
2024-01-10 10:55         ` Stefan Kangas
2024-01-10 22:14           ` JD Smith
2024-01-10 23:20             ` Stefan Kangas

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='CADwFkmk+ynNCm1BY-nTZyXtCK0Pf2Rh4JPDBd41VSJ=V=B4tJQ@mail.gmail.com' \
    --to=stefankangas@gmail.com \
    --cc=57883-done@debbugs.gnu.org \
    --cc=jdtsmith@gmail.com \
    --cc=larsi@gnus.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.
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.