Re: [dev] [st] Fixed -e with support for spaces

2010-11-30 Thread Kurt H Maier
On Tue, Nov 30, 2010 at 5:28 PM, Aurélien Aptel wrote: > A bit off-topic, but i've just noticed both urxvt and xterm exit > successfully no matter what you run. > $ urxvt -e fsjdjsdjfjk && echo yep > yep > $ this is expected, since urxvt and xterm are working properly. if it concerns you, do som

Re: [dev] [st] Fixed -e with support for spaces

2010-11-30 Thread Aurélien Aptel
A bit off-topic, but i've just noticed both urxvt and xterm exit successfully no matter what you run. $ urxvt -e fsjdjsdjfjk && echo yep yep $

Re: [dev] [st] Fixed -e with support for spaces

2010-11-30 Thread Aurélien Aptel
Ok. Tip now has xterm-like -e.

Re: [dev] [st] Fixed -e with support for spaces

2010-11-29 Thread Ethan Grammatikidis
On 29 Nov 2010, at 10:50 pm, Aurélien Aptel wrote: On Sun, Nov 28, 2010 at 10:20 PM, Joseph Xu wrote: Not sure what you mean by breaking argument parsing. I think it's the simplest way to parse a command with complex quoted arguments correctly without having to run an extra shell process.

Re: [dev] [st] Fixed -e with support for spaces

2010-11-29 Thread Aurélien Aptel
On Sun, Nov 28, 2010 at 10:20 PM, Joseph Xu wrote: > Not sure what you mean by breaking argument parsing. I think it's the > simplest way to parse a command with complex quoted arguments correctly > without having to run an extra shell process. It breaks st argument parsing because you have to pu

Re: [dev] [st] Fixed -e with support for spaces

2010-11-28 Thread Josh Rickmar
On Sun, Nov 28, 2010 at 04:20:21PM -0500, Joseph Xu wrote: > > > On 11/28/2010 06:22 AM, Aur??lien Aptel wrote: > > On Sat, Nov 27, 2010 at 12:35 AM, Joseph Xu wrote: > >> came up with. It relies on the shell that executes st to parse the > >> arguments, so you can't run a command like st -e "to

Re: [dev] [st] Fixed -e with support for spaces

2010-11-28 Thread Moritz Wilhelmy
Excerpts from Joseph Xu's message of Sun Nov 28 22:20:21 +0100 2010: > On 11/28/2010 06:22 AM, Aurélien Aptel wrote: > > On Sat, Nov 27, 2010 at 12:35 AM, Joseph Xu wrote: > >> came up with. It relies on the shell that executes st to parse the > >> arguments, so you can't run a command like st -e

Re: [dev] [st] Fixed -e with support for spaces

2010-11-28 Thread Joseph Xu
On 11/28/2010 06:22 AM, Aurélien Aptel wrote: > On Sat, Nov 27, 2010 at 12:35 AM, Joseph Xu wrote: >> came up with. It relies on the shell that executes st to parse the >> arguments, so you can't run a command like st -e "touch arst", you have >> to run st -e touch arst. This also means you can'

Re: [dev] [st] Fixed -e with support for spaces

2010-11-28 Thread Aurélien Aptel
On Sat, Nov 27, 2010 at 12:35 AM, Joseph Xu wrote: > came up with. It relies on the shell that executes st to parse the > arguments, so you can't run a command like st -e "touch arst", you have > to run st -e touch arst. This also means you can't have any st arguments > after the -e because they'l

Re: [dev] [st] Fixed -e with support for spaces

2010-11-26 Thread Joseph Xu
Josh and I were discussing this over IRC. Here's an alternative patch I came up with. It relies on the shell that executes st to parse the arguments, so you can't run a command like st -e "touch arst", you have to run st -e touch arst. This also means you can't have any st arguments after the -e be

[dev] [st] Fixed -e with support for spaces

2010-11-26 Thread Josh Rickmar
Here's a quick fix to pass the opt_cmd to $SHELL -c, which fixes a bug where you couldn't call -e with a command with spaces (arguments to that command). I earlier tried to pass the command directly to execvp() by using strsep to set args, but the code turned out to be far too complex (I think). d