GNU bug report logs - #64198
Feature request: compile.el's "Find this in" prompt should be hookable.

Previous Next

Full log

View this message in rfc822 format

From: Dave Abrahams <dave <at> boostpro.com>
To: Eli Zaretskii <eliz <at> gnu.org>
Cc: 64198 <at> debbugs.gnu.org
Subject: bug#64198: Feature request: compile.el's "Find this in" prompt should be hookable.
Date: Wed, 21 Jun 2023 09:09:08 -0700

[Message part 1 (text/plain, inline)]

> On Jun 21, 2023, at 4:24 AM, Eli Zaretskii <eliz <at> gnu.org> wrote:
> 
>> From: Dave Abrahams <dave <at> boostpro.com>
>> Date: Tue, 20 Jun 2023 15:30:58 -0700
>> 
>> [I hope this is the right venue for feature requests.  If not, sorry!]
> 
> This is the right place.
> 
>> When a file can't be found via the path given in a diagnostic, I'd like to be able to override the prompt that emacs gives to locate the file.  compilation-parse-errors-filename-function happens too early, while the buffer is being initially parsed.  A similar compilation-locate-file-function would be great.  If there's interest I could try to develop a patch.
> 
> Before discussing patches, could you please describe your situation?
> Specifically, how does it happen that neither the compilation
> directory plus the file name shown by the diagnostics nor the search
> of compilation-search-path succeed to locate the file?  And what would
> the hook function you suggest adding do to resolve this, i.e. how
> would it know where to look for the file?

When Swift asserts, it doesn't write the path to the file into the output, because… reasons I grudgingly accept.  So one needs to guess at the file.  https://github.com/apple/swift/issues/66777 contains all the details, but if you want additional info, please ask.

[Message part 2 (text/html, inline)]

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.