On Mon, Jul 04, 2005 at 03:14:06PM +0200, Michal Kochanowicz wrote:
On Mon, Jul 04, 2005 at 02:49:09PM +0200, Artur Frysiak wrote:
What I'm doing is:
1. running konsole
2. ssh to other up-to-date AC-main
3. running screen
4. running VIM
VIM with set nottybuiltin ?
No. I
On Tue, Jul 05, 2005 at 08:41:17AM +0200, Artur Frysiak wrote:
On Mon, Jul 04, 2005 at 03:14:06PM +0200, Michal Kochanowicz wrote:
On Mon, Jul 04, 2005 at 02:49:09PM +0200, Artur Frysiak wrote:
What I'm doing is:
1. running konsole
2. ssh to other up-to-date AC-main
3. running
On Mon, Jul 04, 2005 at 02:49:09PM +0200, Artur Frysiak wrote:
What I'm doing is:
1. running konsole
2. ssh to other up-to-date AC-main
3. running screen
4. running VIM
VIM with set nottybuiltin ?
No. I didn't touch this setting.
--
--= Michal Kochanowicz =--==--==BOFH==--==--=
On Sun, 03 Jul 2005, Michal Kochanowicz wrote:
On Sat, Jul 02, 2005 at 11:10:27PM +0200, Jan Rekorajski wrote:
My proposal is for us to stop being so uber-smart and just revert to
defaults. Kill all those s/xterm/xterm-color/ and s/xterm/we-know-better/
patches and just stick to TERM=xterm
On Sun, Jul 03, 2005 at 11:59:28 +0200, Jan Rekorajski wrote:
I agree, we shall do it the _common_ way.
However Debian/RH/FC has ^H for xterm-color, so following above rule you
should revert ncurses-xterm-color-new.patch, don't you? ;)
That's right, especially when no sane program is
On Sun, 03 Jul 2005, Tomasz Pala wrote:
On Sun, Jul 03, 2005 at 11:59:28 +0200, Jan Rekorajski wrote:
I agree, we shall do it the _common_ way.
However Debian/RH/FC has ^H for xterm-color, so following above rule you
should revert ncurses-xterm-color-new.patch, don't you? ;)
On Fri, Jul 01, 2005 at 13:38:49 +0200, Jan Rekorajski wrote:
a) kill X11-XTerm.ad.patch or s/0x08/\177/ and/or add *VT100*backarrowKey:
false
b) the same with XTerm.ad-pl
c) s/^H/^?/ in terminfo entries for xterm
You didn't read me carefully. This is Debian:
$ echo $TERM; infocmp | grep
On Fri, Jul 01, 2005 at 13:05:36 +0200, Jan Rekorajski wrote:
I'm still waiting for test cases what was wrong with my fix!
I'm getting ^? instead of erased character. Scenario:
a = host without stty erase set
OK, my machine.
b = host with stty erase in bashrc
start X on a
run xterm
On Fri, Jul 01, 2005 at 13:38:49 +0200, Jan Rekorajski wrote:
I got somewhere, first what it looks like on RH 7.3:
[EMAIL PROTECTED] baggins]$ echo $TERM
xterm
H... why have you xterm not xterm-color? They differ...
[EMAIL PROTECTED] baggins]$ infocmp | grep kbs
kbeg=\EOE,
On Thu, Jun 30, 2005 at 18:27:49 +0200, Tomasz Pala wrote:
You could just read this.
Just to be precise: we are screwed, RH has fixed everything (including
broken screen).
Debian is the same. So we've got ridiculous situation: RH/FC/Debian
works everywhere, PLD works fine locally and
10 matches
Mail list logo
