unofficial mirror of notmuch@notmuchmail.org
 help / color / mirror / code / Atom feed
From: Bijan Chokoufe <bijan@chokoufe.com>
To: David Edmondson <dme@dme.org>, Tomi Ollila <tomi.ollila@iki.fi>
Cc: notmuch@notmuchmail.org
Subject: Re: [PATCH] config: Expand ~ to $HOME
Date: Wed, 11 May 2016 19:17:27 +0000	[thread overview]
Message-ID: <CAOsAL0rr2FdG1gPOcaMV_iqORRrXAKYc8wA_YWWjC+TTibar3w@mail.gmail.com> (raw)
In-Reply-To: <m28tzi9vah.heart-of-gold@dme.org>

[-- Attachment #1: Type: text/plain, Size: 754 bytes --]

so what would be the spec for handling ~user?
As Tomi pointed out ~foo will point to different folders if set by user
'foo' or by user 'bar'.
To what folder should it point and where do I get this information?

David Edmondson <dme@dme.org> schrieb am Di., 10. Mai 2016 um 10:22 Uhr:

> On Mon, May 09 2016, Bijan Chokoufe Nejad wrote:
>
> >> ~user is ~ in case you're 'user' -- except that now that I think of it
> >> ~user could read home directory from /etc/passwd and not using $HOME.
> >> If you're 'eve', then ~alice should definitely be different than ~
> >
> > OK I see. I never used ~user instead of ~ and don't see any advantage in
> using
> > ~user but good to know it's there.
>
> A solution that supports ~ but not ~user seems incomplete.
>

[-- Attachment #2: Type: text/html, Size: 1111 bytes --]

  reply	other threads:[~2016-05-11 19:17 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-08 15:49 [PATCH] config: Expand ~ to $HOME Bijan Chokoufe Nejad
2016-05-08 16:47 ` Tomi Ollila
2016-05-08 18:50   ` Bijan Chokoufe
2016-05-09  7:54     ` Tomi Ollila
2016-05-09  8:40       ` Tomi Ollila
2016-05-09 21:57       ` Bijan Chokoufe Nejad
2016-05-10  8:22         ` David Edmondson
2016-05-11 19:17           ` Bijan Chokoufe [this message]
2016-05-11 20:11             ` David Edmondson
2016-05-11 20:16               ` Tomi Ollila

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=CAOsAL0rr2FdG1gPOcaMV_iqORRrXAKYc8wA_YWWjC+TTibar3w@mail.gmail.com \
    --to=bijan@chokoufe.com \
    --cc=dme@dme.org \
    --cc=notmuch@notmuchmail.org \
    --cc=tomi.ollila@iki.fi \
    /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).