Re: [PATCH] Fix tests when using bash_completion

2 messages, 2 authors, 2016-06-15 · open the first message on its own page

Re: [PATCH] Fix tests when using bash_completion

From: Junio C Hamano <hidden>
Date: 2016-06-15 22:43:06

"Ron Parker" [off-list ref] writes:
When using bash_completion, 'cd' echos the target directory name to
standard
out.  If 'cd' participates in a pipe whose output is compared against an
expected value, this causes a false failure report.  Pipe cd's stdout to
/dev/null in these cases.
This is way too ugly.

Are you sure bash-completion is the culprit, not your CDPATH?

Re: [PATCH] Fix tests when using bash_completion

From: Julian Phillips <hidden>
Date: 2016-06-15 22:43:06

On Mon, 23 Apr 2007, Junio C Hamano wrote:
"Ron Parker" [off-list ref] writes:
quoted
When using bash_completion, 'cd' echos the target directory name to
standard
out.  If 'cd' participates in a pipe whose output is compared against an
expected value, this causes a false failure report.  Pipe cd's stdout to
/dev/null in these cases.
This is way too ugly.

Are you sure bash-completion is the culprit, not your CDPATH?
even with bash-completion _and_ CDPATH I only get a print when changing to 
a directory in CDPATH not the current directory ... perhaps an alias set 
for cd?

(I'm not the only one who thinks CDPATH is ick am I? :S)

-- 
Julian

  ---
BOFH Excuse #350:

paradigm shift...without a clutch
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help