From: "Morten Kjærulff" <mortenkjarulff@gmail.com>
To: cygwin@cygwin.com
Subject: Re: Wrong expansion of ~/
Date: Mon, 24 Aug 2020 14:36:25 +0200 [thread overview]
Message-ID: <CA+7cx1o0-GqrYcrwK3A6AFajxmOSFKwD8TosQqTVi9HKsUwCzg@mail.gmail.com> (raw)
In-Reply-To: <83c5ffc2-02ac-e38e-6e8c-9963ac15b62d@towo.net>
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:
> > Hi,
> >
> > 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
If I add:
. ~/.git-completion.bash
if [ ! $? = 0 ] ; then
echo "HOME=" $HOME
echo "~=" ~
echo "~=" ~
echo "~=" ~
echo "~=" ~
echo "~=" ~
echo "~=" ~
echo "~=" ~
echo "~=" ~
fi
I cannot reproduce the issue.
Weird.
/Morten
next prev parent reply other threads:[~2020-08-24 12:36 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 [this message]
2020-08-24 20:39 ` Brian Inglis
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=CA+7cx1o0-GqrYcrwK3A6AFajxmOSFKwD8TosQqTVi9HKsUwCzg@mail.gmail.com \
--to=mortenkjarulff@gmail.com \
--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).