Invalid symbolic links on the module source path

Florian Weimer fw at
Sun Jul 19 09:52:22 UTC 2020

* Andrew Dinn:

> On 19/07/2020 09:01, Florian Weimer wrote:
>> Emacs creates dangling symbolic links while source files are edited,
>> as a form of lock file.  These have names of the form ""
>> (for a source file called  Should javac skip reading these
>> non-source files, based on their name?
>> Presently, javac attempts to open these files and reports an error,
>> terminating the compilation.
>> (I wonder if there is a reasonably straightforward way to work around
>> this using a JavaFileManager.)
> I actually like this behaviour because it stops me rebuilding whren I
> have unsaved edits to JDK sources (n.b. the JVM build also fails if it
> picks up one of these files via a wildcard substitution).
> So ... it's not a bug it's a feature -- and quite a useful one as far as
> I am concerned ;-)

That's actually a good point.  I was triggering rebuilds once .#*.java
files popped up.  Those rebuilds obviously fail all the time.  Once I
started ignore .#* files in the change detection logic, the experience
is actually fairly pleasant.

More information about the compiler-dev mailing list