After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 766037 - Poor parsing of %s in "Standard Programs" configuration
Poor parsing of %s in "Standard Programs" configuration
Status: RESOLVED OBSOLETE
Product: gnome-commander
Classification: Other
Component: application
1.4.x
Other Linux
: Normal minor
: 1.4
Assigned To: GNOME Commander maintainer(s)
GNOME Commander maintainer(s)
Depends on:
Blocks:
 
 
Reported: 2016-05-05 19:50 UTC by c1659869
Modified: 2018-08-03 18:06 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description c1659869 2016-05-05 19:50:50 UTC 
GNOME Commander 1.4.8, Fedora 23 LXDE.
In configuring GCMD to use LXTerminal, the following line must be used for "Terminal:"

lxterminal --working-directory=" %s "

Note that LXTerminal currently has no way of specifying the working directory other than "--working-directory=DIR".
The saner syntax below doesn't work because of poor parsing in GCMD:

lxterminal --working-directory=%s

Please fix GCMD such that the above line parses correctly.
Comment 1 Uwe Scholz 2016-05-08 21:38:07 UTC 
Thank you for taking the time for this bug report.

I'm not really sure if it is a bug what you described. I tested the usage of lxterminal within gcmd and it turns out that you don't need '--working-directory=...' at all. Gcmd always executes the command given in the 'terminal' text field in the active directory pane. So you can remove the working directory argument for lxterminal for firing up a terminal session in the current directory.

If this doesn't solve your problem, don't hesitate to give an example on what you would like to achive and what the actual result is.
Comment 2 GNOME Infrastructure Team 2018-08-03 18:06:14 UTC 
-- GitLab Migration Automatic Message --

This bug has been migrated to GNOME's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.gnome.org/GNOME/gnome-commander/issues/73.