Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 06 Jul 2018 13:09:23 +0000
From:      bugzilla-noreply@freebsd.org
To:        ports-bugs@FreeBSD.org
Subject:   [Bug 229567] sysutils/tmux: pane_current_path support is broken
Message-ID:  <bug-229567-7788@https.bugs.freebsd.org/bugzilla/>

next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D229567

            Bug ID: 229567
           Summary: sysutils/tmux: pane_current_path support is broken
           Product: Ports & Packages
           Version: Latest
          Hardware: Any
                OS: Any
            Status: New
          Severity: Affects Many People
          Priority: ---
         Component: Individual Port(s)
          Assignee: mat@FreeBSD.org
          Reporter: 0mp@FreeBSD.org
             Flags: maintainer-feedback?(mat@FreeBSD.org)
          Assignee: mat@FreeBSD.org

A user might want to create a new pane which starts a shell inside the curr=
ent
working directory. tmux has a mechanism for it since about version 1.9, whi=
ch
is called "pane_current_path". It can be used in the following way in a tmux
command:

    split-window -h -c "#{pane_current_path}"

Unfortunately, the mechanism is broken using on tmux 2.7 on FreeBSD
12.0-CURRENT amd64 and FreeBSD 11.2 i386. It looks like the function which =
is
supposed to generate the value for the "pane_current_path" returns an empty
string or something. As a result new panes are always opened in the home
directory even if the default path where tmux was originally started is not=
 the
home directory.

--=20
You are receiving this mail because:
You are the assignee for the bug.=



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-229567-7788>