unofficial mirror of notmuch@notmuchmail.org
 help / color / mirror / code / Atom feed
From: Carl Worth <cworth@cworth.org>
To: Ralph Seichter <ralph@ml.seichter.de>, notmuch@notmuchmail.org
Subject: Re: Relative directories for database-mail_root and -path?
Date: Mon, 28 Oct 2024 10:23:39 -0700	[thread overview]
Message-ID: <87cyjkywdg.fsf@wondoo.home.cworth.org> (raw)
In-Reply-To: <D55XO36NCNJP.1M80U9LGS5D3Y@ml.seichter.de>

On Sat, Oct 26 2024, Ralph Seichter wrote:
> I made quite a hash of this, didn't I? I even quoted the manpage's URL
> in my original question, because that was naturally the first place I
> checked, but I missed the relevant paragraph:

No apology needed!

I just went to double-check the man page myself. I first read the
details of 'database.mail_root' and then 'database.path'. When I didn't
find the detail there, I also read the section below on 'DATABASE
LOCATION'.

I still hadn't found anything about relative paths, but since I had the
email from David telling me this was documented there, I went back and
searched (computationally, not visually) for "relative" and finally
found the sentence you found as well:

>   The available configuration items are described below. Non-absolute
>   paths are presumed relative to $HOME for items in section database.

It's in its own sentence before the details of any specific
configuration item.

So I did just demonstrate that it's an easy thing to miss. That's not a
short man page, and it will generally be used as a reference (looking
for details of one specific entry, not reading the entire page straight
through).

In spite of the redundancy, perhaps it would make sense to add:

	A non-absolute path is presumed relative to $HOME.

to the descriptions of each of:

	database.backup_dir
        database.hook_dir
        database.mail_root
        database.path

(And if someone does this, they should also check whether git.path
deserves the same treatment.)

-Carl

  parent reply	other threads:[~2024-10-28 17:37 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 [this message]
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
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=87cyjkywdg.fsf@wondoo.home.cworth.org \
    --to=cworth@cworth.org \
    --cc=notmuch@notmuchmail.org \
    --cc=ralph@ml.seichter.de \
    /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).