Hello!
Stephan Sokolow has written on Saturday, 24 November, at 7:26:
>The other problem which pops up with arguments is that, while XTerm
>accepts the input to -e as either one big argument or a sequence of them:
>xterm -e "bash -c 'echo foo; read'"
>...urxvt REQUIRES it to be pre-parsed and passed as one urxvt argument
>per exec() argument:
>urxvt -e bash -c 'echo foo; read'
All terminals accept pre-parsed syntax and only few may reparse them
(as in your example above) so I would suggest to always parse arguments
if you use terminal, i.e. always use syntax similar to used for urxvt.
Another problem is some terminal emulators use -e before program name
with arguments and some use -x. It's one of reasons why I've added the
file terminals.list into libfm version 1.2.0.
>Both approaches make sense (xterm's is easier for lxpanel-style use
>while urxvt's discourages application developers from writing or finding
>potentially buggy quoting routines that can lead to vulnerabilities)
>Unfortunately, since non-xterm terminals like LXTerminal only accept the
>"all in one argument" approach, we can't all just use URxvt's syntax either.
False statement. Every terminal (including LXTerminal, yes) accepts
the arguments after command. Just try it and you'll see. :)
But '-e' / '-x' dilemma cannot be resolved so easily.
With best regards.
Andriy.
------------------------------------------------------------------------------
Monitor your physical, virtual and cloud infrastructure from a single
web console. Get in-depth insight into apps, servers, databases, vmware,
SAP, cloud infrastructure, etc. Download 30-day Free Trial.
Pricing starts from $795 for 25 servers or applications!
http://p.sf.net/sfu/zoho_dev2dev_nov
_______________________________________________
Lxde-list mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/lxde-list
