martanne / dvtm Goto Github PK

It usually happen while creating dvtm on TTY and using it in X11, but I also got it in TTY once it have been attached to X11 first. I don't get any issue while using it only in TTY or X11 without attaching in the each other.

While attaching in both TTY and X11 with abduco, display is not properly updated, as for vim, or less ^D for half page down. This cause the buffer to be updated at the upper part, and seldomly for the lower part.

This also makes the sequence ^[[?6c appears:

• Randomly while typing;
• Systematically at the moment I attach dvtm on X11 after creating dvtm in TTY
• Systematically while pressing down some key on TTY, where the repetition frequency is higher (less time between two repetition);
• Periodically, like every second, without touching the keyboard. I only got it once.

I tried to change the -d delay option delay either very high (10000) or very low (0), without significant result.

The way I checked was in vim, where the entered keys are displayed.
After waiting a few, the ^[[?6c disappear from vim modeline, and the typed keys got executed (like ^[[?6cdddddddddd is displayed in vim echo area, then after 1 second, only ^[[?6c is displayed and 10 lines are deleted).

Thank you for developping this multiplexer. I really like it. I can try to help, so don't hesitate asking me more details or twinkering the source.

Hi,

I just discovered dvtm and started loving it for my Pi, but I have a question.

Is it possible to bind the super key (windows key) as MOD? I tried Mod4Mask but that's for X11 if i remember well.

Thanks, and thanks for dvtm!

My PS1 shows directories in terminal title and some have accents and others non-ASCII characters but dvtm doesn’t display it.
For example:
Without dvtm: ~/LycéeXP/math
With dvtm: ~/LyceXP/math

The doc says that Shift-PageUp should scroll back but it does not work.
The shortcut Mod-PageUp works thought.
Could you please add the missing shortcut.
Thanks.

I love dvtm!

However, there is some problem while using base16-shell.
chriskempson/base16-shell#84

The latest ncurses release has mainlined dvtm's normal and -256color terminfo files. Installing them here overrides the ncurses's package and will cause conflicts for package managers.

(Also, congrats on their getting mainlined!)

The X11 window title is, as best I can see, very broken.

In a clean testing environment, with nothing in my .bashrc except the exact example here, I found that the title usually updates after a 30 second delay.

In my personal environment under zsh, whether or not the title gets updated is a coin toss. Sometimes it will after a lengthy delay, but most often it will hold on to a specific title that has long since lost relevance.

Each shell window within dvtm has its own title rendered by dvtm, and those work just fine. For whatever reason, dvtm is struggling to correctly set _NET_WM_NAME to the currently active shell window's title.

Interestingly, the title WILL update in less or vim if I perform the action I described here: #14 (comment)
It looks like the text bleed through I'm seeing in that issue is in fact an X11 window title, for some reason getting dumped into the terminal output.

abduco -c session_name will automatically start dvtm. How can I set a non default escape key to dvtm?
I've put an alias to basrch as alias dvtm=dvtm -e ^Oo but that only works if I run dvtm on its own.

Even when dvtm is compiled without mouse support, vim running within dvtm does not react to mouse events.

There's several ways to get to this frozen shell problem since upgrading to 10.11. I don't know enough about C to help, but I would take a wild guess that it relates to OS X's new SIPS.

• Quit a window with the key binding (e.g. in my case C-d q)
• Type exit at a shell
• Open and then close the buffer mode pager thingy (e.g. in my case C-d e to open a scrollback buffer in less which I gather has something to do with copying and pasting but I just use it for scrolling)

This causes the window to basically freeze, In essence I can spawn windows but not close them.

On @martanne's advice I ran the following after intentionally causing the issue.

Which seemed to point to this line of code.

I've tried this with clean user configs (bashrc, profile etc), on two different machines and with clean installs of dvtm using the unmodified default config.

Hope someone can help because I've been using this thing daily for years now and I really miss it!

As I grow more and more disenchanted with X, I am more and more enticed by the notion of moving to a workflow that consists of yaft, abduco and dvtm. However, one thing I love about yaft is its support for libsixel. This allows me to keep whatever small graphical things around I might still want.

Is there any chance that dvtm (and abduco, if applicable) could get support for libsixel?

Hi,

I haven't investigated this issue, all I can say is that I'm using zsh with dvtm 0.15 and alt-backspace inserts a newline instead of doing a ^W.

Thanks.

@varmanishant
Don't know it's the same like this one:
#20
but since there is no image or something else, I open a new issue.

First my env:

SHELL=/bin/zsh
TERM=xterm-256color
DVTM_TERM=dvtm
LC_COLLATE=C
ABDUCO_CMD=/home/demonking/bin/dvtm-status
MANPAGER=manpager
PYENV_SHELL=zsh
DVTM_EDITOR=/usr/local/bin/vis
LC_CTYPE=en_US.UTF-8
ABDUCO_SOCKET_DIR=/tmp
DVTM=v0.15-38-g945f094
DVTM_WINDOW_ID=6

VM env:

$ env
XDG_SESSION_ID=13
rvm_bin_path=/usr/local/rvm/bin
TERM=xterm-256color
SHELL=/bin/bash
rvm_stored_umask=0022
USER=vagrant
_system_type=Linux
rvm_path=/usr/local/rvm
rvm_prefix=/usr/local
MAIL=/var/mail/vagrant
PATH=/usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games:/opt/puppetlabs/bin:/usr/local/rvm/
bin:/home/vagrant/bin
rvm_loaded_flag=1
LC_COLLATE=C
PWD=/home/vagrant
LANG=de_DE.UTF-8
_system_arch=x86_64
PS1=\n[$bold][$black][[$dk_blue]@[$black]]-[[$green]\u[$yellow]@[$green][$black]
]-[[$pink]\w[$black]][\033[0;33m]$(__vcs_name) [\033[00m][$reset]\n[$reset]$
_system_version=8
rvm_version=1.27.0 (latest)
SHLVL=1
HOME=/home/vagrant
LOGNAME=vagrant
LC_CTYPE=en_US.UTF-8
XDG_RUNTIME_DIR=/run/user/1000
rvm_user_install_flag=0
_system_name=Debian
_=/usr/bin/env

How I have caused this mess ?

$ ls -l
$ vi io.h

After I quit "vi" with :q the mess starts.
I have only pressed "Return" multiple times

When I clear my screen, everything is fine, but it's annoying.

I'm getting the wrong background color under the following conditions. First I set the background color of all dvtm's ui elements to cyan (it looks fine with my color scheme). This seems to work - dvtm elements are cyan and windows have a normal background - until a window sets the terminal title. After that, the window uses cyan as a background color even in the shell!

I've reproduced this under gnome-terminal and st, and my shell prompt doesn't use any colors.

Hi,

My main editor is Kakoune, and I can't seem to get it to render properly in a dvtm session. The first "frames" are rendered just fine, but a couple seconds after I've started typing things in, the status bar starts being rendered over the buffer, text randomly disappears, whitespace get inserted into the buffer etc. Using MOD+r always resets the terminal back to what it should be though (everything is displayed properly).

I've tried changing the DVTM_TERM variable to screen/xterm, using ncurses5 over ncurses6, and I've read issues seemingly relevant that have already been created, but nothing I've tried has had any effect on the glitch.

What can I do to pinpoint precisely the cause of this faulty rendering, and how can I work around/fix it ?

Thanks.

Building against netbsd-curses appears to build successfully, but launching dvtm 0.15 as dvtm or DVTM_TERM=rxvt-unicode dvtm (urxvt) or DVTM_TERM=st-256color dvtm (st) results in a no-op terminal window that cannot accept any input and must be killed to exit.

==> Starting build()...
cleaning
cleaning
dvtm build options:
CC dvtm.c
CC vt.c
CFLAGS = -march=native -O2 -pipe -fstack-protector-all -fomit-frame-pointer -std=c99 -I. -DVERSION="0.15" -DNDEBUG -D_FORTIFY_SOURCE=2 -D_POSIX_C_SOURCE=200809L -D_XOPEN_SOURCE=700 -D_XOPEN_SOURCE_EXTENDED
LDFLAGS = -Wl,-z,now -Wl,-O1,--sort-common,--as-needed,-z,relro -lc -lutil -lcurses -lterminfo
CC = cc
vt.c: In function ‘vt_forkpty’:
vt.c:1636:4: warning: ignoring return value of ‘chdir’, declared with attribute warn_unused_result [-Wunused-result]
chdir(cwd);
^~~~~~~~~~
CC -o dvtm
==> Entering fakeroot environment...
==> Starting package()...
stripping executable
installing executable file to /tmp/dvtm/pkg/dvtm/usr/bin
installing manual page to /tmp/dvtm/pkg/dvtm/usr/share/man/man1
installing terminfo description
2 entries and 0 aliases written to dvtm.info.cdb
==> Tidying install...
-> Removing doc files...
-> Removing libtool files...
-> Removing static library files...
-> Stripping unneeded symbols from binaries and libraries...
-> Compressing man and info pages...
==> Checking for packaging issue...
==> Creating package "dvtm"...
-> Generating .PKGINFO file...
-> Generating .BUILDINFO file...
-> Generating .MTREE file...
-> Compressing package...
100 % 32.1 KiB / 100.0 KiB = 0.321
==> Leaving fakeroot environment.
==> Finished making: dvtm 0.15-2 (Sat Nov 12 16:00:34 UTC 2016)

dvtm.info.cdb terminfo database is built un the source directory (expected). However, dvtm.info.cdb is not installed to /usr/share/terminfo automatically per the default config.mk (not expected). No problem. Modifying the dvtm PKGBUILD recipe to install dvtm.info.cdb to /usr/share/terminfo and setting TERMINFO=/usr/share/terminfo does not resolve the no-op issue (not expected). Modifying config.mk and the build recipe to install dvtm.info.cdb to $HOME with TERMINFO set accordingly does not resolve the issue either. How to get dvtm up and running?

I am running into an issue with using dvtm with vim. When I open vim from a dvtm window, I could move to the right pane <Ctrl-L>, but not move back to the left pane <Ctrl-h>.

Here is my vim mapping for this action https://github.com/tnguyen14/dotfiles/blob/master/home/.vimrc#L126

I could still do the default command <Ctrl-w><Ctrl-l> and <Ctrl-w><Ctrl-h>, just not the remapped keys.

Does anyone have any suggestion?

dvtm doesn't draw lines on Open BSD, instead it shows weird characters (compiled with -lncursesw).

Hi,

when running dvtm inside a dtach session, it can validly happen that you're later attaching from a different terminal type than the one you initially used. This means dvtm will output invalid escape sequences. E.g. try attaching back and forth from TERM=linux and TERM=xterm. You'll notice corruption. Even worse on FreeBSD, as cons25w is quite different from xterm.

Also, dtach doesn't really have the ability of handling this either (it can't influence the environment of a child process, sure, but there also isn't another hook facility for something like this). Remember, unlike dvtm, dtach is a simple attach/detach program without any terminal conversion functionalities.

tmux and screen both handle this - so there should be a way for dtach/dvtm to handle this too, right?

My current workaround is running dtach inside each dvtm window, instead of dvtm inside dtach, but that approach clearly loses the layout each time I reattach and provides no scrollback. So instead I'm proposing this:

• Give dvtm a command (e.g. via the commands FIFO) to update the value of $TERM and reinitialize ncurses.
• Then I can write a script that uses this command to set the new terminal type before attaching using dtach.

Is this doable?

is that on purpose (why)?

it doesn't do that when i set DVTM_TERM to "screen" or "xterm" before launching dvtm, or if i set TERM to either of those from within dvtm.

but with that there's at least one (new) issue: the cursor isn't properly reset, or something - let's say my cursor is somewhere in the middle of the screen (for example, after i do "echo -e 'foo\nfoo\nfoo\nfoo\nfoo'). then, when i open and close some fullscreen program (e.g. "man man"), the cursor is suddenly on the 1st line of the screen, not where it was before, and the output from before (the 5 "foo"s) is still there.

is that expected behavior?

thanks!

(btw this happens with dvtm-0.15 on linux)

I often have multiple tags displayed at once, and it gets a bit hard to know which window has which tag: I need to switch to each individual tag and check if my window is there.

What I propose is having the name of the tags displayed in the window bar, next to the title.

I made this patch:

diff --git a/Makefile b/Makefile
index 09d1080..baba2f6 100644
--- a/Makefile
+++ b/Makefile
@@ -16,13 +16,13 @@ config.h:

 .c.o:
    @echo CC $<
-   @${CC} -c ${CFLAGS} $<
+   @${CC} -c -lm ${CFLAGS} $<

 ${OBJ}: config.h config.mk

 dvtm: ${OBJ}
    @echo CC -o $@
-   @${CC} -o $@ ${OBJ} ${LDFLAGS}
+   @${CC} -o $@ ${OBJ} -lm ${LDFLAGS}

 debug: clean
    @make CFLAGS='${DEBUG_CFLAGS}'
diff --git a/dvtm.c b/dvtm.c
index c6440ab..ddf2f39 100644
--- a/dvtm.c
+++ b/dvtm.c
@@ -13,6 +13,7 @@
 #include <stdlib.h>
 #include <unistd.h>
 #include <stdint.h>
+#include <math.h>
 #include <wchar.h>
 #include <sys/select.h>
 #include <sys/stat.h>
@@ -405,9 +406,20 @@ draw_border(Client *c) {
        c->title[maxlen] = '\0';
    }

-   mvwprintw(c->window, 0, 2, "[%s%s#%d]",
+   char tagnames[12 * LENGTH(tags)] = "";
+
+   for (int j = c->tags, i = LENGTH(tags) - 1; i >= 0; --i) {
+       if (j >= pow(2, i)) {
+           j = j - pow(2, i);
+           strcat(tagnames, tags[i]);
+           strcat(tagnames, " | ");
+       }
+   }
+
+   mvwprintw(c->window, 0, 2, "[%s%s%s#%d]",
              *c->title ? c->title : "",
              *c->title ? " | " : "",
+             tagnames,
              c->order);
    if (t)
        c->title[maxlen] = t;

I am a beginner with C, so it may not be written in a very good C: I used the pow() function and then had to use one more library just for this.

Hi There,
I'm building dvtm from source. I've tried both the 0.15 tarball release and the master branch from the GitHub repo. I'm running from within VirtualBox.

My build appears to work correctly: https://gist.github.com/GrooveStomp/19900f5f6ad4b9398fefa929e1337078

When running I get a segfault: https://imgur.com/a/hKeDg

I've recorded a debugging session that hopefully illuminates what's going on: https://gist.github.com/GrooveStomp/1ad5b0029cbbcfb18f4c5043fe2f58d4

I've tried reading through the code and making sense of it, but there are a few too many concepts at play that I'm not familiar with, so I figured it was time to reach out to the author. :-)

I got the following error whilst tryting to install dvtm via homebrew:
"dvtm: This formula either does not compile or function as expected on macOS
versions newer than Yosemite due to an upstream incompatibility."

Version info:
macOS Sierra 10.12.1 (16B2555)
homebrew 1.1.1

As of now, I'm not using tags, so I would like to hide the tag bar.
This is probably already possible, because the dvtm in the Ubuntu repos is like that. But I can't get it to work editing config.h. I tried const char tags[][8] = {}; but that didn't get rid of the whole line.

Start dvtm, run in it:

for ((I = 1; I <= 100; ++I)) { echo $I; }; mc

Then make outer terminal slightly bigger, then exit from mc. You will see something like this:

92
93
94
95
96
97
  2016-12-19 18:43:31  ~$
99
100

So, terminal clearly corrupted.
dvtm 0.15. gnome-terminal 3.22.1. debian stretch.

Occasionally while using dvtm, opening a curses application that does not fill up the entire page shows some lines from a previously-open curses session.

In particular, when git log does not fill the entire page, there is occasionally some extra text at the top of the screen that appears to be left over from the last time I ran git log or from the last time I ran vim, whichever was most recent.

What about using box drawing characters for tag symbols? This make them harder to type, but much prettier onscreen:

• │├┤ tiling right
• ├┬┤ tiling bottom
• ├┴┤ tiling top
• ├─┤ vertical stack
• ├┼┤ grid
• │ │ fullscreen
• │@│ spiral
• │&│ dwindle

We are totally sure that these characters are supported, as they are those already composing the interface.

We can also add the character associated with the keybinding next to them, so that user can discover these keybindings by cycling through the layouts.

If you want those I can make a patch, otherwise it is OK to close the issue.

Is there a way to setup some of the keybindings without the need to use MOD as a "prefix"?
a first try using { { (0x17), 'h', }, { focusleft, { NULL } } }, for <ALT>+<h> - please correct me if i'm wrong here - did not work.

See martanne/abduco#3

Hi,
I am using dvtm 0.14 on current OpenBSD with korn shell.
my .profile sources the .kshrc with all aliases like ll="ls -la"

after starting dvtm, I dont see any of my aliases.
It seems that dvtm does not read neither .profile, nor .kshrc
So wehn using dvtm, after I create a new shell, I always have to manually source my .kshrc.

questions:

1. are any dot-files sourced by dvtm on its statup? If yes what are they called and where are they expected?
2. how can I tweak dvtm to source my ~/.kshrc

thanks,
Alex.

I like to use less as my DVTM_EDITOR for search and copying. I'd like to be able to use less --RAW-CONTROL-CHARS to maintain colorized output when entering copy/paste mode.

thanks in advance!

I tried setting the modifier to Ctrl + Space, but I could not get any result, the mapping simply being ignored.

I tested the following in my config.h:

#define MOD  CTRL(' ')

#define MOD  CTRL('@')

#define MOD  CTRL('<control-space-character>')

The control space character have been inserted with vim, with <c-v> <c-space> which inserted something represented as ^@.

You may know better than me how terminal keyboard input is complex, and this is not really a priority for me.

Thank you for having a look at this, and for starting up this great project.

I use the base16 tomorrow theme and the blue used by dvtm was a little off so I changed it from 68 to 4.

I've ended up defining a basic set of colors that I use in other customizations what do you think about adding something like the following to the default config.def.h?

--- config.def.h        2015-11-06 10:32:53.000023000 -0600
+++ config.def.h.modified       2015-11-06 10:30:39.000353000 -0600
@@ -13,12 +13,26 @@

 enum {
        DEFAULT,
+       BLACK,
+       RED,
+       GREEN,
+       YELLOW,
        BLUE,
+       MAGENTA,
+       CYAN,
+       WHITE,
 };

 static Color colors[] = {
-       [DEFAULT] = { .fg = -1,         .bg = -1, .fg256 = -1, .bg256 = -1, },
-       [BLUE]    = { .fg = COLOR_BLUE, .bg = -1, .fg256 = 68, .bg256 = -1, },
+       [DEFAULT] = { .fg = -1,            .bg = -1, .fg256 = -1, .bg256 = -1, },
+       [BLACK]   = { .fg = COLOR_BLACK,   .bg = -1, .fg256 = 0,  .bg256 = -1, },
+       [RED]     = { .fg = COLOR_RED,     .bg = -1, .fg256 = 1,  .bg256 = -1, },
+       [GREEN]   = { .fg = COLOR_GREEN,   .bg = -1, .fg256 = 2,  .bg256 = -1, },
+       [YELLOW]  = { .fg = COLOR_YELLOW,  .bg = -1, .fg256 = 3,  .bg256 = -1, },
+       [BLUE]    = { .fg = COLOR_BLUE,    .bg = -1, .fg256 = 4,  .bg256 = -1, },
+       [MAGENTA] = { .fg = COLOR_MAGENTA, .bg = -1, .fg256 = 5,  .bg256 = -1, },
+       [CYAN]    = { .fg = COLOR_CYAN,    .bg = -1, .fg256 = 6,  .bg256 = -1, },
+       [WHITE]   = { .fg = COLOR_WHITE,   .bg = -1, .fg256 = 7,  .bg256 = -1, },
 };

 #define COLOR(c)        COLOR_PAIR(colors[c].pair)

Using the latest git versions of fish, dvtm and st, I get the following corruption by just holding down enter:

augusto $
augusto $
augusto $
augustoaugusto $
augusto $
augusto $
augusto $

This happens very reliably and the corrupted line augustoaugusto $ does not scroll up unless a new line (anything other than augusto $) is added at the bottom (if I call ls, for example). When I do, this corrupted line "becomes" a normal line and scrolls up.

If I do call ls on a buffer such as the one above and hold down enter, more corrupted lines are generated, and scroll up along with the output of ls until that output is out of the viewport. After that, the lines just float there, stuck.

This doesn't seem to happen with bash within dvtm+st, or with fish+st without dvtm. Weird.

there was an error in v0.15 where sigwinch seems to be 'undefined' within default includes in osx

actually seems available on sys/signal.h but doesn't compile.

added definition if not defined already.

homebrew patchfile: https://github.com/Homebrew/formula-patches/blob/master/dvtm/patch-vt.h-compat.patch

Hi,

when I use the ls command on my terminal while using dvtm, colors doesn't appear. However, everything else - like Vim for example - works fine. Is there a way to correct it ?

My configuration:

• OS: Parabola GNU/Linux-libre ;
• WM: dwm ;
• Terminal: st ;
• dvtm compiled from sources.

Thanks.

Using ^[ as a modifier, to use either Escape then key, or directly Alt + key.

It already works, I can switch window with Alt + j but I then need to press any key, which will be sent to the client.

Would it be easy to fix? If not, Ctrl + Space is pretty great already.

I am having a lot of fun with dvtm and abduco. Thank you!

Hi,

Would you consider adding support for a configuration file ?

A simple ini-type file that allows setting defaults for the command line flags would be nice, as I basically only use dvtm with the -c flag, and don't want to litter my shell with a dedicated alias (or recompile it every-time there's a new version out). I also like to version my configuration files with vcsh so I can deploy my dot files easily to a new system, and I can't do that with dvtm at the moment because I would have to recompile dvtm on every system I want it on.

Thanks.

To reproduce:
https://www.cl.cam.ac.uk/~mgk25/ucs/examples/UTF-8-demo.txt
$ (printf "\033]0;moo\007"; mcview ~/x/txt/UTF-8-demo.txt) in one terminal running dvtm' and xdotool search --name moo key slash t h a i Return sleep 1 key Up F7' somewhere else.

My config.mk:

# dvtm version
VERSION = 0.14

# Customize below to fit your system

PREFIX ?= /usr/local
MANPREFIX = ${PREFIX}/man
# specify your systems terminfo directory
# leave empty to install into your home folder
TERMINFO := ${DESTDIR}${PREFIX}/share/terminfo

INCS = -I.
LIBS = -lc -lutil -lncurses
CPPFLAGS = -D_POSIX_C_SOURCE=200809L -D_XOPEN_SOURCE=700 -D_XOPEN_SOURCE_EXTENDED -D__BSD_VISIBLE
CFLAGS += -std=c99 ${INCS} -DVERSION=\"${VERSION}\" -DNDEBUG ${CPPFLAGS}
LDFLAGS += ${LIBS}

DEBUG_CFLAGS = ${CFLAGS} -UNDEBUG -O0 -g -ggdb -Wall -Wextra -Wno-unused-parameter

CC ?= cc
STRIP ?= strip

The error i'm getting when running make:

cleaning
dvtm build options:
CFLAGS   = -O2 -pipe   -std=c99 -I. -DVERSION="0.14" -DNDEBUG -D_POSIX_C_SOURCE=200809L -D_XOPEN_SOURCE=700 -D_XOPEN_SOURCE_EXTENDED -D__BSD_VISIBLE
LDFLAGS  =  -lc -lutil -lncurses
CC       = cc
CC dvtm.c
CC vt.c
CC -o dvtm
dvtm.o: In function `drawbar':
dvtm.c:(.text+0x272b): undefined reference to `waddnwstr'
cc: error: linker command failed with exit code 1 (use -v to see invocation)
*** Error code 1

Stop.

What about having both:

I may be able to try it after my exams if you are short on time.

I hope dvtm can implement truecolor support.

https://gist.github.com/XVilka/8346728

I'm not sure how to describe this issue properly so I've attached some screenshots.
I start with a some what clean 3 window setup:

Then, I run some commands so the prompt will be lower in the window, and launch vim:

When I exit vim, the prompt returns to the top of the window, as you can see in the following screenshots (the cursor blinks on the 'l' of the 'locate' command). The desired behavior is for it to return at the same location where a CLI program was called.

After pressing some 'Enter's you can see that the prompt overrides outputs from previous commands.

I'm using mate-terminal + abduco + dvtm. I tried to mess a bit with DVTM_TERM / TERM, and tried using xterm instead of mate-terminal, but I get the same result. To be honest, I am not sure what causing it or even if it is a dvtm issue.

Thanks.
(Edit: Fixed a typo)
(Update: Solved by setting TERM as 'rxvt-256color' in bashrc, not sure why though)

I get buffer corruption when I use ncmpcpp. Currently I am using termite -> adbuco -> dvtm -> ncmpcpp. This happens with st -> dvtm -> ncmpcpp also. dvtm is really a nice tool that even with these bugs I try to make it work.

I’d like to launch command in dvtm (equivalent of screen: ^a:screen <command>). Maybe something vim/screen-like to configure dvtm while running.

Hello I am thinking about forking dvtm because I want some really dwm behaviour. I don't want to press the modkeys CTRL+g first.. I just want to press Mod4+Enter for spawning another window. What do you mean is this possible or not?

best regards

Chris

Hi,
Alt+Backspace (delete word backwards) in bash, does not work with dvtm.
I'm using mate-terminal + abduco + dvtm.
(I know I can still use Ctrl+w, but I wonder why the specific keybinding does not work anymore)
Thanks.

printf "\e[9mstrikethrough\e[0m\n"
works in st doesn't in dvtm

The proc filesystem is not implemented across all POSIX platforms (e.g. OS X, OpenBSD, deprecated in FreeBSD, etc.) and dvtm uses a procfs lookup for static char *getcwd_by_pid(Client *c) to implement the Mod-C command.

lsof is messy but portable. May be worth exploring as an alternative.