unofficial mirror of notmuch@notmuchmail.org
 help / color / mirror / code / Atom feed
From: Pengji Zhang <me@pengjiz.com>
To: Ralph Seichter <ralph@ml.seichter.de>, notmuch@notmuchmail.org
Subject: Re: Relative directories for database-mail_root and -path?
Date: Sat, 26 Oct 2024 10:53:33 +0800	[thread overview]
Message-ID: <87o73760cy.fsf@pengjiz.com> (raw)
In-Reply-To: <D55848YAPK5H.DYS1MEQ4V5EG@ml.seichter.de>

"Ralph Seichter" <ralph@ml.seichter.de> writes:

> Looking at [1], I am trying to figure out if/how the semantic
> equivalent of the pseudo configuration
>
> 	[database]
> 	mail_root = ~/.maildir
> 	path = ~/.local/share/notmuch/default
>
> can be achieved? The docs don't mention that '~' has any special
> meaning, and my tests agree. How then does one specify directories
> relative to the user's $HOME ? Simply dropping the ~/ prefix and using
> .maildir or .local does not seem to work either. I found the latter
> being suggested in some Internet search result or other, and thought
> I'd give it a try, but no dice.

I suppose dropping the prefix should work? In 'lib/config.cc':

--8<---------------cut here---------------start------------->8---
static char *
_expand_path (void *ctx, const char *key, const char *val)
{
    char *expanded_val;

    if ((strcmp (key, "database.path") == 0 ||
	 strcmp (key, "database.mail_root") == 0 ||
	 strcmp (key, "database.hook_dir") == 0 ||
	 strcmp (key, "database.backup_path") == 0 ) &&
	val[0] != '/')
	expanded_val = talloc_asprintf (ctx, "%s/%s", getenv ("HOME"), val);
    else
	expanded_val = talloc_strdup (ctx, val);

    return expanded_val;
}
--8<---------------cut here---------------end--------------->8---

So if the value does not start with '/', it is considered relative to
the home directory.

What does 'notmuch config list' show for you?

Pengji

  reply	other threads:[~2024-10-26  3:02 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 [this message]
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
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=87o73760cy.fsf@pengjiz.com \
    --to=me@pengjiz.com \
    --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).