From: "Ralph Seichter" <ralph@ml.seichter.de>
To: <notmuch@notmuchmail.org>
Subject: Re: [PATCH] Add support for ~/foo style relative paths
Date: Thu, 31 Oct 2024 21:19:55 +0100 [thread overview]
Message-ID: <D5A9QC7YTECT.JVAK2UAQCIAV@ml.seichter.de> (raw)
In-Reply-To: <87frocscss.fsf@tethera.net>
* David Bremner:
> what should we do if val[1] != '/'?
My patch assumes that the answer to this question is "nothing". The
string "~xyz" would expand to "/home/alicexyz" instead of, say,
"/home/xyz" if notmuch is run by user alice.
It is not a very useful expansion, but it does what it says on the tin,
and saves the extra effort of parsing /etc/passwd: Tilde expands to the
process owner's home directory, no matter what character follows next.
Mind you, I don't object to being able to reference other users' home
directories. I just don't quite see how useful that ability would be,
given the private nature of email. Am I missing an obvious usecase here?
-Ralph
next prev parent reply other threads:[~2024-10-31 20:27 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-25 22:00 Relative directories for database-mail_root and -path? Ralph Seichter
2024-10-26 2:53 ` Pengji Zhang
2024-10-26 14:49 ` Ralph Seichter
2024-10-26 17:16 ` David Bremner
2024-10-26 18:02 ` Ralph Seichter
2024-10-28 7:36 ` Tomi Ollila
2024-10-28 17:23 ` Carl Worth
2024-10-28 19:10 ` Ralph Seichter
2024-10-29 5:44 ` Tomi Ollila
2024-10-29 22:15 ` [PATCH] Add support for ~/foo style relative paths Ralph Seichter
2024-10-31 11:59 ` David Bremner
2024-10-31 13:42 ` Tomi Ollila
2024-10-31 20:19 ` Ralph Seichter [this message]
2024-11-01 14:12 ` David Bremner
2024-11-01 15:13 ` Tomi Ollila
2024-11-01 19:57 ` Ralph Seichter
2024-11-02 17:33 ` Tomi Ollila
2024-11-02 19:00 ` Ralph Seichter
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
List information: https://notmuchmail.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=D5A9QC7YTECT.JVAK2UAQCIAV@ml.seichter.de \
--to=ralph@ml.seichter.de \
--cc=notmuch@notmuchmail.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 public inbox
https://yhetil.org/notmuch.git/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).