> On Sun, Dec 04, 2011 at 03:58:36PM +0100, Romain Francoise wrote:
>> I think I spoke too fast. KERN_FILE_BYPID only gives you the inode number
>> of the cwd and the mountpoint of the filesystem where it's located.
>
> Hm. That sucks... looks like getcwd() works by walking each vnode on
> the
Nicholas Marriott writes:
> Can we do this on ANY platform apart from Linux?
Solaris, with procfs. That's about it, I think.
--
Romain Francoise
http://people.debian.org/~rfrancoise/
--
All the data continuously gene
On Sun, Dec 04, 2011 at 03:58:36PM +0100, Romain Francoise wrote:
> I think I spoke too fast. KERN_FILE_BYPID only gives you the inode number
> of the cwd and the mountpoint of the filesystem where it's located.
Hm. That sucks... looks like getcwd() works by walking each vnode on
the way up to
> > Ok cool.
>
> I got the window copy part of it done. I don't know how the status one
> should work...there's no way to get the character to jump to without
> using the status line (or to wait for it silently like vi, but that may
Well, we already wait for escape silently. I don't really mind T
I'm pretty sure you won't get much testing for stuff that isn't in (I
never have), so your best bet is to test as well you can then send it
out and if there are problems we can fix them as we go.
On Sun, Dec 04, 2011 at 04:03:00PM +, Nicholas Marriott wrote:
> Cool, thanks for working on this
Cool, thanks for working on this stuff.
I meant to mention before but when you send patches could you please
either:
a) send one patch for one change, ie don't split them up with so much
granularity, eg man page change can be in the same diff file as the
code.
b) or if you prefer, give each set
On Sat, Dec 03, 2011 at 06:05:44PM +0100, Matthias Lederhofer wrote:
> Nicholas Marriott wrote:
> > Hmm. As far as I can see xterm doesn't set PWD, how come xterm doesn't
> > have this problem?
> >
> > If you make sure your shell exports PWD and add it to
> > update-environment, tmux will set it
I think I spoke too fast. KERN_FILE_BYPID only gives you the inode number
of the cwd and the mountpoint of the filesystem where it's located.
Finding the name of the directory from that requires walking the entire
filesystem, which is obviously out of the question...
So I guess we're back to squar
