From: Jean Louis <bugs@gnu.support>
To: help-gnu-emacs@gnu.org
Subject: Re: Function to find symlink target
Date: Thu, 2 Jun 2022 08:15:21 +0300 [thread overview]
Message-ID: <YphHacarJj7NvieB@protected.localdomain> (raw)
In-Reply-To: <87v8tjnbin.fsf@dataswamp.org>
* Emanuel Berg <incal@dataswamp.org> [2022-06-02 03:44]:
> This is the same use case that has been mentioned several
> times by now! Maybe that's the only things symlinks are
> good for?
Maybe you have been following your "rule" to avoid symlinks without
researching what you can do with symlinks.
Main use for symlinks on a GNU system is in libraries' directories:
lrwxrwxrwx 1 11 May 16 2020 aspell -> aspell-0.60
lrwxrwxrwx 1 17 Apr 28 12:55 terminfo -> ../share/terminfo
lrwxrwxrwx 1 22 Mar 25 2021 libauthcustom.so -> libauthcustom.so.0.0.0
lrwxrwxrwx 1 22 Mar 25 2021 libauthcustom.so.0 -> libauthcustom.so.0.0.0
-rwxr-xr-x 1 14K Mar 25 2021 libauthcustom.so.0.0.0
lrwxrwxrwx 1 20 Mar 25 2021 libauthldap.so -> libauthldap.so.0.0.0
lrwxrwxrwx 1 20 Mar 25 2021 libauthldap.so.0 -> libauthldap.so.0.0.0
-rwxr-xr-x 1 87K Mar 25 2021 libauthldap.so.0.0.0
lrwxrwxrwx 1 21 Mar 25 2021 libauthmysql.so -> libauthmysql.so.0.0.0
lrwxrwxrwx 1 21 Mar 25 2021 libauthmysql.so.0 -> libauthmysql.so.0.0.0
-rwxr-xr-x 1 75K Mar 25 2021 libauthmysql.so.0.0.0
lrwxrwxrwx 1 19 Mar 25 2021 libauthpam.so -> libauthpam.so.0.0.0
lrwxrwxrwx 1 19 Mar 25 2021 libauthpam.so.0 -> libauthpam.so.0.0.0
-rwxr-xr-x 1 14K Mar 25 2021 libauthpam.so.0.0.0
lrwxrwxrwx 1 21 Mar 25 2021 libauthpgsql.so -> libauthpgsql.so.0.0.0
lrwxrwxrwx 1 21 Mar 25 2021 libauthpgsql.so.0 -> libauthpgsql.so.0.0.0
-rwxr-xr-x 1 63K Mar 25 2021 libauthpgsql.so.0.0.0
lrwxrwxrwx 1 20 Mar 25 2021 libauthpipe.so -> libauthpipe.so.0.0.0
lrwxrwxrwx 1 20 Mar 25 2021 libauthpipe.so.0 -> libauthpipe.so.0.0.0
-rwxr-xr-x 1 14K Mar 25 2021 libauthpipe.so.0.0.0
lrwxrwxrwx 1 19 Mar 25 2021 libauthpwd.so -> libauthpwd.so.0.0.0
lrwxrwxrwx 1 19 Mar 25 2021 libauthpwd.so.0 -> libauthpwd.so.0.0.0
-rwxr-xr-x 1 14K Mar 25 2021 libauthpwd.so.0.0.0
lrwxrwxrwx 1 22 Mar 25 2021 libauthshadow.so -> libauthshadow.so.0.0.0
lrwxrwxrwx 1 22 Mar 25 2021 libauthshadow.so.0 -> libauthshadow.so.0.0.0
-rwxr-xr-x 1 14K Mar 25 2021 libauthshadow.so.0.0.0
lrwxrwxrwx 1 22 Mar 25 2021 libauthsqlite.so -> libauthsqlite.so.0.0.0
lrwxrwxrwx 1 22 Mar 25 2021 libauthsqlite.so.0 -> libauthsqlite.so.0.0.0
-rwxr-xr-x 1 55K Mar 25 2021 libauthsqlite.so.0.0.0
lrwxrwxrwx 1 22 Mar 25 2021 libauthuserdb.so -> libauthuserdb.so.0.0.0
lrwxrwxrwx 1 22 Mar 25 2021 libauthuserdb.so.0 -> libauthuserdb.so.0.0.0
-rwxr-xr-x 1 30K Mar 25 2021 libauthuserdb.so.0.0.0
lrwxrwxrwx 1 29 Mar 25 2021 libcourierauthcommon.so -> libcourierauthcommon.so.0.0.0
lrwxrwxrwx 1 29 Mar 25 2021 libcourierauthcommon.so.0 -> libcourierauthcommon.so.0.0.0
-rwxr-xr-x 1 42K Mar 25 2021 libcourierauthcommon.so.0.0.0
lrwxrwxrwx 1 33 Mar 25 2021 libcourierauthsaslclient.so -> libcourierauthsaslclient.so.0.0.0
lrwxrwxrwx 1 33 Mar 25 2021 libcourierauthsaslclient.so.0 -> libcourierauthsaslclient.so.0.0.0
-rwxr-xr-x 1 14K Mar 25 2021 libcourierauthsaslclient.so.0.0.0
lrwxrwxrwx 1 27 Mar 25 2021 libcourierauthsasl.so -> libcourierauthsasl.so.0.0.0
lrwxrwxrwx 1 27 Mar 25 2021 libcourierauthsasl.so.0 -> libcourierauthsasl.so.0.0.0
-rwxr-xr-x 1 14K Mar 25 2021 libcourierauthsasl.so.0.0.0
lrwxrwxrwx 1 23 Mar 25 2021 libcourierauth.so -> libcourierauth.so.0.0.0
lrwxrwxrwx 1 23 Mar 25 2021 libcourierauth.so.0 -> libcourierauth.so.0.0.0
However, I can't tell how is that system managed, it apparently works
fine without my user's intervention.
Here are more practical example on finding files easier in file system
by using symlinks for tagging:
What's a good solution for file-tagging in linux? - Super User
https://superuser.com/questions/81563/whats-a-good-solution-for-file-tagging-in-linux
Another interesting file tagging system:
TMSU
https://tmsu.org/
--
Jean
Take action in Free Software Foundation campaigns:
https://www.fsf.org/campaigns
In support of Richard M. Stallman
https://stallmansupport.org/
next prev parent reply other threads:[~2022-06-02 5:15 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-18 20:55 Function to find symlink target Jean Louis
2022-05-18 23:00 ` Emanuel Berg
2022-05-22 13:52 ` Jean Louis
2022-05-22 18:02 ` Emanuel Berg
2022-05-23 9:05 ` Jean Louis
2022-05-23 20:46 ` Emanuel Berg
2022-05-24 0:59 ` Emanuel Berg
2022-05-24 1:09 ` Michael Heerdegen
2022-05-24 2:14 ` Emanuel Berg
2022-05-24 2:27 ` Michael Heerdegen
2022-05-24 8:04 ` Emanuel Berg
2022-05-24 8:52 ` Michael Heerdegen
2022-05-25 5:54 ` Michael Heerdegen
2022-05-27 2:25 ` Jean Louis
2022-05-27 3:31 ` Michael Heerdegen
2022-05-27 8:00 ` Jean Louis
2022-05-27 14:47 ` Emanuel Berg
2022-05-28 6:43 ` Jean Louis
2022-05-28 15:29 ` Emanuel Berg
2022-05-28 15:43 ` Emanuel Berg
2022-05-28 16:08 ` Eli Zaretskii
2022-05-28 16:46 ` Emanuel Berg
2022-05-28 16:55 ` Eli Zaretskii
2022-05-28 17:05 ` Emanuel Berg
2022-05-31 6:27 ` Jean Louis
2022-05-31 12:24 ` Emanuel Berg
2022-05-31 6:31 ` Jean Louis
2022-05-31 12:16 ` Emanuel Berg
2022-06-01 7:43 ` Jean Louis
2022-06-02 0:40 ` Emanuel Berg
2022-06-02 5:15 ` Jean Louis [this message]
2022-06-05 5:40 ` Emanuel Berg
2022-05-25 5:05 ` Jean Louis
2022-05-25 22:33 ` Emanuel Berg
2022-05-29 2:01 ` Emanuel Berg
2022-05-19 23:14 ` Nick Dokos
2022-05-20 0:42 ` Emanuel Berg
2022-05-23 8:17 ` Jean Louis
2022-05-23 22:49 ` Michael Heerdegen
2022-05-23 22:57 ` Emanuel Berg
2022-05-24 0:59 ` Michael Heerdegen
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=YphHacarJj7NvieB@protected.localdomain \
--to=bugs@gnu.support \
--cc=help-gnu-emacs@gnu.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.