From: Brian Inglis <Brian.Inglis@SystematicSw.ab.ca>
To: cygwin@cygwin.com
Subject: Re: Wrong expansion of ~/
Date: Mon, 24 Aug 2020 14:39:42 -0600 [thread overview]
Message-ID: <6b79f1aa-04ef-99ce-443e-08fe475f5948@SystematicSw.ab.ca> (raw)
In-Reply-To: <CA+7cx1o0-GqrYcrwK3A6AFajxmOSFKwD8TosQqTVi9HKsUwCzg@mail.gmail.com>
On 2020-08-24 06:36, Morten Kjærulff via Cygwin wrote:
> On Mon, Aug 24, 2020 at 11:52 AM Thomas Wolff wrote:
>> Am 24.08.2020 um 10:05 schrieb Morten Kjærulff via Cygwin:
>>> I have a script that starts several tmux panes with my favorite commands.
>>> In some (*some* and only *sometimes*) of the panes I see:
>>>
>>> -bash: /home/xxxxxP/.git-completion.bash: No such file or directory
>>> -bash: /home/xxxxxP/.git-prompt.sh: No such file or directory
>>>
>>> My .bashrc has:
>>>
>>> $ grep git .bashrc
>>> . ~/.git-completion.bash
>>> . ~/.git-prompt.sh
>>>
>>> My userid is xxxxxf (and not xxxxxP).
>>>
>>> Is this known?
>> What if you trace `echo $HOME; echo ~` after the `.`? I have occasional
>> cases where $HOME and ~ start to be different in my shell, which is
>> quite weird and should not happen according to bash documentation.
>
> Ok,
>
> My userid is xx00mkf.
>
>
> If I add:
>
> . ~/.git-completion.bash
> if [ ! $? = 0 ] ; then
> echo "HOME=" $HOME
> echo "~=" ~
> fi
>
> I see:
>
> -bash: /home/xx00m/.git-completion.bash: No such file or directory
> HOME= /home/xx00mkf
> ~= /home/xx00m
>
>
> If I add:
>
> . ~/.git-completion.bash
> if [ ! $? = 0 ] ; then
> echo "HOME=" $HOME
> echo "~=" ~
> echo "~/.git-completion.bash=" ~/.git-completion.bash
> fi
>
> -bash: /home/xx00m/.git-completion.bash: No such file or directory
> HOME= /home/xx00mkf
> ~= /home/xx00mkf
> ~/.git-completion.bash= /home/xx00mkf/.git-completion.bash
HOME dir depends on entries in:
/etc/nsswitch.conf
whether you have /etc/passwd and/or /etc/group files and their entries;
your SAM and/or AD entry contents including e.g.
$ net user $USER | grep '^Comment'
Comment <cygwin home="/home/..." group="Users"...>
You can check if any of these are in effect by running:
$ getent passwd $USER
If you think they are relevant, you might also want to try to trace and debug
your bash-completion setup scripts:
$ set -vx
$ . /etc/profile.d/bash_completion.sh |& tee /tmp/completion.log | less
to see what they are doing that might affect other settings.
--
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada
This email may be disturbing to some readers as it contains
too much technical detail. Reader discretion is advised.
[Data in IEC units and prefixes, physical quantities in SI.]
next prev parent reply other threads:[~2020-08-24 20:39 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-24 8:05 Morten Kjærulff
2020-08-24 9:50 ` Thomas Wolff
2020-08-24 12:36 ` Morten Kjærulff
2020-08-24 20:39 ` Brian Inglis [this message]
2020-08-25 7:15 ` Morten Kjærulff
2020-08-25 12:58 ` Brian Inglis
2020-08-27 7:44 ` Morten Kjærulff
2020-08-27 16:49 ` rifter
2020-08-27 17:56 ` Thomas Wolff
2020-08-28 6:29 ` Morten Kjærulff
2020-08-27 17:54 ` Jim Garrison
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=6b79f1aa-04ef-99ce-443e-08fe475f5948@SystematicSw.ab.ca \
--to=brian.inglis@systematicsw.ab.ca \
--cc=cygwin@cygwin.com \
/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.
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).