Re: systemd @ in filenames not supported by thing-at-point

[Emanuel Berg]

Yuri Khan wrote:

> As you surely know, on *nix, every character
> is valid in a filename, except for NUL and
> slash; and every character is valid in a file
> path, except for NUL.
>
> However, we expect all kinds of parentheses,
> brackets and angle brackets to close around
> file paths. #include <foo/bar.h>

Either way it will break something whatever
you do.

If I was in charge of the systemd project,
I wouldn't have used "@" or any such unusual
char in a filename, and

    $ find ~ -name \*@\* | wc -l
    0

However

    $ sudo find / -name \*@\* | wc -l
    1164

(far from all of them are systemd related).

As expected tho,

    $ sudo find / -name \*@\* | grep -i emacs | wc -l
    0

:)

> I do not know of other instances of @ used as
> a delimiter next to a file name.

There are @ in shell scripting (e.g. zsh),
shell programming (Perl), Makefiles as you
mention, LaTeX relies heavily on it, Biblatex
has it for every entry, Lisp has it (the ,@
insert of a list), they are obviously in email
addresses and remote access (ssh etc.), and
doesn't Java come with some crappy
documentation system where the @s act much like
comment delimiters? And the functional
languages have it. And others!

However they doesn't seem to occur with
filenames that often (but sometimes), which
makes it tempting to include it in the list for
quick access to the 1164 or whatever
files above.

Granted, many of those are typically not files
that you edit but rather bunches of data.

One thing to be considered is that systemd is
now all over the Unix world despite some big
money splinter efforts.

Like everyone else, I don't know anything about
it, and I don't like it, but I do use it :)

-- 
underground experts united .... http://user.it.uu.se/~embe8573
Emacs Gnus Blogomatic ......... http://user.it.uu.se/~embe8573/blogomatic
                   - so far: 64 Blogomatic articles -