On Tuesday, 27 January 2026 21:09:37 GMT G. Branden Robinson wrote:
> Hi Deri,
>
> At 2026-01-27T20:55:40+0000, Deri wrote:
> > On Tuesday, 27 January 2026 19:33:03 GMT G. Branden Robinson wrote:
> > > At 2026-01-27T20:25:48+0100, Bruno Haible wrote:
> > > > ... On Manjaro 23, there is an empty directory named '_Inline'
> > > > created in the user's home directory. It's a little negative
> > > > surprise.
> > >
> > > Huh! There's one lurking in my $HOME, too--I never noticed! It's dated
> > > 29 December 2024, so not due to a recent change.
> > >
> > > > I guess it comes from src/devices/gropdf/gropdf.pl ?
> > >
> > > Deri, any idea what this is about?
> > >
> > > Does this have to do with the optimized font subsetting feature (written
> > > in C, IIRC)?
> > >
> > > It's kind of gross to litter the user's home directory like this. :(
> >
> > The information is at the top of page 3 of this document you have seen
> > several times.
>
> Indeed it is, and indeed I have. Thanks for the reminder.
>
> It says:
>
> "Inline::C creates a work directory in your home directory called
> "_Inline", if you would prefer it used somewhere else then set
> environment variable PERL_INLINE_DIRECTORY to a writeable directory."
>
> Is this a commonplace convention in the Perl community, or something you
> innovated for gropdf?
Hi Branden,
The Inline man page says:-
=========================================================================
The Inline ’directory’
Inline needs a place to build your code and to install the results
of the build. It uses a single directory named '.Inline/' under
normal circumstances. If you create this directory in your home di‐
rectory, the current directory or in the directory where your pro‐
gram resides, Inline will find and use it. You can also specify it
in the environment variable "PERL_INLINE_DIRECTORY" or directly in
your program, by using the "directory" keyword option. If Inline
cannot find the directory in any of these places it will create a
'_Inline/' directory in either your current directory or the direc‐
tory where your script resides.
==========================================================================
I could embed ~/.Inline in the code if that is considered better.
Cheers
Deri
> Regards,
> Branden
