On Sat 26 Nov 2011 08:28:26 AM PST, Patrick Haller wrote:
> autocmd BufEnter * cd %:p:h
> for when you use multiple buffers in vim.
set autochdir
--
Bus error -- please leave by the rear door.
signature.asc
Description: PGP signature
On 2011-11-25 22:42, Julian Dammann wrote:
> > It's all about spatial locality.
> Ever tried ":!your_terminal &" in vim? Maybe that's good enough for you if
> bound to some key.
autocmd BufEnter * cd %:p:h
for when you use multiple buffers in vim.
On Fri 25 Nov 2011 10:42:31 PM PST, Julian Dammann wrote:
> > It's all about spatial locality. When I'm editing some code in Vim,
> > I like to launch some new terminals (or file managers) in the same
> > working directory as the file I'm editing to do additional things.
>
> Ever tried ":!your_te
> It's all about spatial locality. When I'm editing some code in Vim,
> I like to launch some new terminals (or file managers) in the same
> working directory as the file I'm editing to do additional things.
Ever tried ":!your_terminal &" in vim? Maybe that's good enough for you if
bound to some
On 25 November 2011 20:39, Suraj N. Kurapati wrote:
> Yes, and that's good enough for me. However, in the case that the
> remote client's title contains a path that also exists on the local
> machine (perhaps network mounted on both local & remote machines)
> then your newly launched program will
On Fri 25 Nov 2011 10:11:35 AM PST, Kurt Van Dijck wrote:
> Suraj N. Kurapati wrote:
> >the ability to open new programs in the currently focused
> >client's workdir.
> >https://github.com/sunaku/.dwm/compare/tip...spawn_cwd
>
> I don't understand the feature.
It's all about spatial locality. Whe
On Fri 25 Nov 2011 01:00:58 PM PST, Bastien Dejean wrote:
> Troels Henriksen a écrit :
>
> > look for the process indicated by the _NET_WM_PID property, then
> > use the working directory of that process.
>
> It seems the value of _NET_WM_PID is not always useful: For urxvtc
> clients, it is equal
Troels Henriksen a écrit :
> Alternative/additional idea: look for the process indicated by the
> _NET_WM_PID property, then use the working directory of that process.
It seems the value of _NET_WM_PID is not always useful:
For urxvtc clients, it is equal to the pid of urxvtd.
--
Bastien
Kurt Van Dijck writes:
> On Fri, Nov 25, 2011 at 09:54:44AM +0100, Troels Henriksen wrote:
>> "Suraj N. Kurapati" writes:
>>
>> > On Thu 24 Nov 2011 05:12:17 PM PST, Stephen Paul Weber wrote:
>> >> Somebody signing messages as Suraj N. Kurapati wrote:
>> >> >the ability to open new programs in
On Fri, Nov 25, 2011 at 09:54:44AM +0100, Troels Henriksen wrote:
> "Suraj N. Kurapati" writes:
>
> > On Thu 24 Nov 2011 05:12:17 PM PST, Stephen Paul Weber wrote:
> >> Somebody signing messages as Suraj N. Kurapati wrote:
> >> >the ability to open new programs in the currently focused client's
>
"Suraj N. Kurapati" writes:
> On Thu 24 Nov 2011 05:12:17 PM PST, Stephen Paul Weber wrote:
>> Somebody signing messages as Suraj N. Kurapati wrote:
>> >the ability to open new programs in the currently focused client's
>> >workdir. https://github.com/sunaku/.dwm/compare/tip...spawn_cwd
>>
>> D
On Thu 24 Nov 2011 05:12:17 PM PST, Stephen Paul Weber wrote:
> Somebody signing messages as Suraj N. Kurapati wrote:
> >the ability to open new programs in the currently focused client's
> >workdir. https://github.com/sunaku/.dwm/compare/tip...spawn_cwd
>
> Does this patch just work on xterm/rxv
Somebody signing messages as Suraj N. Kurapati wrote:
one of the things I missed from my previous WMII configuration was the
ability to open new programs in the currently focused client's workdir.
So I ported this feature to DWM using just 27 SLOC in this[2] patch,
[2]: https://github.com/sunak
13 matches
Mail list logo
