On 10/18/13 at 03:05pm, Alexander S. wrote:
> 2013/10/18 Raphaël Proust :
> > On Fri, Oct 18, 2013 at 11:28 AM, Manolo Martínez
> > wrote:
> >> On 10/18/13 at 06:12pm, Chris Down wrote:
> >>> On 2013-10-18 12:03, Manolo Martínez wrote:
> >>> Environments only propagate to children, not their paren
2013/10/18 Raphaël Proust :
> On Fri, Oct 18, 2013 at 11:28 AM, Manolo Martínez
> wrote:
>> On 10/18/13 at 06:12pm, Chris Down wrote:
>>> On 2013-10-18 12:03, Manolo Martínez wrote:
>>> Environments only propagate to children, not their parents. You'll need to
>>> get
>>> the pwd of the currently
On 2013-10-18 11:35, Raphaël Proust wrote:
> AFAIU: if you `cd` in urxvt, the pwd of the urxvt process will change.
> If you `vim` and then `:cd` then pwd of the urxvt process will not
> change (i.e. the parent process (urxvt) keeps its pwd, while the child
> process (vim) will have a new pwd).
In
On Fri, Oct 18, 2013 at 11:28 AM, Manolo Martínez
wrote:
> On 10/18/13 at 06:12pm, Chris Down wrote:
>> On 2013-10-18 12:03, Manolo Martínez wrote:
>> Environments only propagate to children, not their parents. You'll need to
>> get
>> the pwd of the currently focussed window if you want to do th
On 10/18/13 at 06:12pm, Chris Down wrote:
> On 2013-10-18 12:03, Manolo Martínez wrote:
> > > I guess what you want is the pwd of the client that currently has
> > > focus… I also need something like that for plumb(1)ing purposes
> >
> > That's probably what I want, yes. Thanks.
>
> Environments o
On 2013-10-18 12:03, Manolo Martínez wrote:
> > I guess what you want is the pwd of the client that currently has
> > focus… I also need something like that for plumb(1)ing purposes
>
> That's probably what I want, yes. Thanks.
Environments only propagate to children, not their parents. You'll nee
On Fri, Oct 18, 2013 at 11:03 AM, Manolo Martínez
wrote:
> On 10/18/13 at 10:49am, Raphaël Proust wrote:
>>
> Well, the following mouthful does it in fish (mutatis mutandis for other
> shells):
>
> pwdx (xdotool getwindowpid (xdotool getwindowfocus))
In urxvt:
$ xdotool getwindowpid $(xdotool
On 10/18/13 at 10:49am, Raphaël Proust wrote:
> I guess what you want is the pwd of the client that currently has
> focus… I also need something like that for plumb(1)ing purposes
That's probably what I want, yes. Thanks.
> (relative file paths not resolving correctly otherwise). I didn't
> man
On Fri, Oct 18, 2013 at 10:34 AM, Manolo Martínez
wrote:
>> Secondly, you never make it clear *who's* working directory you want to read.
>> Do you always want to be in dwm's working directory? The working directory
>> from
>> the environment you are currently in (which may not be the same as dwm
Thanks for your reply, Chris:
On 10/18/13 at 05:22pm, Chris Down wrote:
> You should include the project you're referring to in your subject, otherwise
> we have to guess what you're talking about. I guess this is about dwm, but
> still...
Of course! I'm sorry; I confess this is "the dwm and dmen
10 matches
Mail list logo
