Your message dated Wed, 13 Apr 2016 21:58:18 +0100
with message-id <[email protected]>
and subject line Re: Bug#719553: gnome-terminal's --working-directory option
does not accept paths that use ~ as reference to the home directory
has caused the Debian Bug report #719553,
regarding gnome-terminal's --working-directory option does not accept paths
that use ~ as reference to the home directory
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
719553: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=719553
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: gnome-terminal
Version: 3.8.3-1
Severity: Normal
The abnormal behavior that I want to report is linked to the
--working-directory option.
Let's say I am the user jmazel whose home directory is /home/jmazel. I have
a directory called Storage in my home directory: /home/jmazel/Storage.
Description of abnormal behavior:
When I open a new terminal with the command "gnome-terminal
--working-directory=~/Storage", the result of pwd in the new terminal is
"/home/jmazel".
Description of expected behavior:
I expected the current directory of the new terminal to be
"/home/jmazel/Storage".
Notes:
*If I open the new terminal using the --working-directory option with an
absolute path ("/home/jmazel/Storage") or a relative path ("Storage"), the
result of pwd in the new terminal is indeed "/home/jmazel/Storage"
*I think that this problem indirectly causes the commands (from contextual
menu or File->*) and shortcuts "Open in a new tab" and "Open in a new
window" to fail to open their new gnome-terminals in the same path as the
terminal they are launched from. In fact, in my case, the path of every new
terminal launched through any of these methods is invariably /home/jmazel.
uname -a
Linux johan-optiplex990 3.9-1-amd64 #1 SMP Debian 3.9.8-1 x86_64 GNU/Linux
dpkg --status libc6-dev
Package: libc6-dev
Status: install ok installed
Priority: optional
Section: libdevel
Installed-Size: 11581
Maintainer: GNU Libc Maintainers <[email protected]>
Architecture: amd64
Multi-Arch: same
Source: eglibc
Version: 2.17-7
Provides: libc-dev
Depends: libc6 (= 2.17-7), libc-dev-bin (= 2.17-7), linux-libc-dev
Recommends: gcc | c-compiler
Suggests: glibc-doc, manpages-dev
Breaks: binutils (<< 2.20.1-1), binutils-gold (<< 2.20.1-11), cmake (<<
2.8.4+dfsg.1-5), gcc-4.4 (<< 4.4.6-4), gcc-4.5 (<< 4.5.3-2), gcc-4.6 (<<
4.6.0-12), libhwloc-dev (<< 1.2-3), libjna-java (<< 3.2.7-4), liblouis-dev
(<< 2.3.0-2), liblouisxml-dev (<< 2.4.0-2), make (<< 3.81-8.1), pkg-config
(<< 0.26-1)
Conflicts: libc0.1-dev, libc0.3-dev, libc6.1-dev
Description: Embedded GNU C Library: Development Libraries and Header Files
Contains the symlinks, headers, and object files needed to compile
and link programs which use the standard C library.
Homepage: http://www.eglibc.org
--- End Message ---
--- Begin Message ---
On Thu, 26 Jun 2014 at 11:45:30 +0200, Egmont Koblinger wrote:
> You can use a space instead of '=', i.e.:
> gnome-terminal --working-directory ~/Storage
> It'll work as you'd expect.
>
> It's a feature of the *shell* that it looks up the home directory if
> the '~' is the first character of a word. If you use '=' as separator
> then '~' is not the first character and hence the shell doesn't expand
> it.
>
> The '~' itself, when literally part of a filename, does not refer to a
> home directory and should remain a literal '~'. It's only the shell
> (and a few more apps that deliberately choose to mimic the shell's
> behavior) that treats '~' specially.
>
> So, gnome-terminal works as expected.
Yes, this. This isn't a bug, pretty much everything else that parses
long options will not expand the tilde in "command --foo=~/bar", for
example:
% mv --target-directory=~/tmp ~/tmp/build/gnome-terminal
mv: failed to access '~/tmp': No such file or directory
% mv --target-directory ~/tmp ~/tmp/build/gnome-terminal
(works, no output)
On Tue, 13 Aug 2013 at 10:29:06 +0900, Johan Mazel wrote:
> *I think that this problem indirectly causes the commands (from contextual
> menu
> or File->*) and shortcuts "Open in a new tab" and "Open in a new window" to
> fail to open their new gnome-terminals in the same path as the terminal they
> are launched from.
I think that's a separate issue. See /usr/share/doc/libvte-2.91-0/README.Debian
for the steps needed to make this work. Unfortunately it can't be made more
automatic because Debian doesn't have a directory in /etc that is sourced by
the standard /etc/bash.bashrc, /etc/zsh/zshrc etc.; this can't happen without
input from the shells' maintainers.
Regards,
S
--- End Message ---
