aboutsummaryrefslogtreecommitdiffhomepage
path: root/src/rbtree.cpp
diff options
context:
space:
mode:
authorRobin Haberkorn <robin.haberkorn@googlemail.com>2015-03-12 04:19:11 +0100
committerRobin Haberkorn <robin.haberkorn@googlemail.com>2015-03-12 04:19:11 +0100
commit4dced2c9d230b88e910e46a78e3e559792520ae1 (patch)
treee6c9c358ed1a70193178b8327b256ca8b01a8680 /src/rbtree.cpp
parent7ceabb232364a4dca0d2418ad1b0dfd01168b145 (diff)
downloadsciteco-4dced2c9d230b88e910e46a78e3e559792520ae1.tar.gz
improved ncurses batch mode initialization
* I now understand better why the old initialization worked ;-) By not calling initscr(), we could prevent some terminal setup and screen clearing usually performed which would interfere with with having a clean stdout stream. However the Curses screen was still basically attached to the terminal. * That's why there was screen flickering in urxvt when calling sciteco (even in batch mode). Also that's why calling batch-mode SciTECO did not work from other Curses programs (including SciTECO). * The new implementation directs Curses at /dev/null, so it will completely stay away from /dev/tty. * /dev/tty is associated with the Curses screen only when the interactive mode is initialized. This works elegantly via freopen() - there's no need to create a new Curses screen. * This does currently not work on PDCurses where the batch mode will still initscr() followed by endwin(). I should investigate how newterm() behaves there - especially on Windows.
Diffstat (limited to 'src/rbtree.cpp')
0 files changed, 0 insertions, 0 deletions