..just for reference, from konsole/src/ProcessInfo.cpp, includes omitted:
> virtual bool LinuxProcessInfo::readCurrentDir(int pid)
> {
> QFileInfo info( QString("/proc/%1/cwd").arg(pid) );
>
> const bool readable = info.isReadable();
>
> if ( readable && info.isSymL
Cool. So basically we need to implement KERN_PROC_CWD on OpenBSD,
although I don't think I would do it the way DragonFly does, I would
probably add a new level 3 sysctl like KERN_PROC_ARGS.
Lemme see if I have time to look at it this week.
On Mon, Dec 05, 2011 at 10:08:55AM +0100, marcel partap
Hi,
I just found out about "mouse-resize-pane" but I'm having some issues using
it in conjunction with "mode-mouse".
Here is my mouse setup:
# grep mouse .tmux.conf
set-option -g mouse-select-pane on
set-option -g mouse-resize-pane on
set-option -g mouse-select-window on
set-window-option -g mode
> Disabling "mode-mouse" fix the issue(s), but is there a way to keep
> mode-mouse enabled and not have this clicks issues, is that PuTTY related ?
It's an issue with the curses lib sometimes sending bogus mouse events.
Problem is that these can be filtered and i beliebe tmux tries to, but
it on
Nicholas Marriott wrote:
> I'm not really convinced by all the PWD talk, the canonical way to find
> the current working directory is to call getcwd(). Not to use PWD, that
> is just a shell convenience. I don't think applications should ever need
> to check PWD rather than calling getcwd(). They
On Mon, Dec 05, 2011 at 06:28:59PM +0100, Matthias Lederhofer wrote:
> Nicholas Marriott wrote:
> > I'm not really convinced by all the PWD talk, the canonical way to find
> > the current working directory is to call getcwd(). Not to use PWD, that
> > is just a shell convenience. I don't think app
phew, mind twisting TAILQ_* macros..but it works now. The problem
you described is gone with this, and also this patch allows for complex
mouse click patterns (like kill window on triple middle button click
then shift left click within one second).. that needs a config syntax
though. and ye
Nicholas Marriott wrote:
> Well, not necessarily, ksh for example does not export PWD.
I could not verify this (on openbsd):
matled@openbsd:~% ksh
$ cd /tmp/b
$ env |grep ^PWD
/tmp/b
$ sh -c pwd
/tmp/b
$ env -i sh -c pwd
/tmp/a
> > What do you mean by the last tw
