On Monday, 22 August 2005, at 11:29:18 (-0400),
Jim Perrin wrote:
> Case 1: with ~/.Eterm
> [EMAIL PROTECTED] Eterm]$ echo $ETERM_THEME_ROOT
> /home/jperrin/.Eterm/themes/Eterm
>
> [EMAIL PROTECTED] Eterm]$ echo $ETERM_USER_ROOT
> /home/jperrin/.Eterm/themes/Eterm
>
> (gdb) print rs_cutchars
> $
>
> Okay, the difference here is that the theme.cfg being used changes.
> What are the contents of ~/.Eterm/themes/Eterm/theme.cfg?
>
The difference is simpler than that. Apparently I was still using my
old config file, which had a bad cut_chars value in user.cfg.
Regenerating a new config solve
On 8/22/05, Michael Jennings <[EMAIL PROTECTED]> wrote:
>
> It sounds like it might be related to the cut_chars option (internal
> variable rs_cutchars). Can you run under gdb and check that
> variable's value in each circumstance? Also, please report the values
> of $ETERM_THEME_ROOT and $ETER
On Monday, 22 August 2005, at 09:54:22 (-0400),
Jim Perrin wrote:
> I can reproduce this on CentOS 4.1, with current Eterm from CVS. It
> for whatever reason seems to be related to the config file. If I rm
> -rf the .Eterm dir and run Eterm I get normal select behavior. When
> .Eterm is present, e
> I can't reproduce anything like that here. Have you tried getting
> Eterm from CVS?
>
I can reproduce this on CentOS 4.1, with current Eterm from CVS. It
for whatever reason seems to be related to the config file. If I rm
-rf the .Eterm dir and run Eterm I get normal select behavior. When
.Et
On Saturday, 20 August 2005, at 11:39:31 (-0500),
Bill Richards wrote:
> I'm using Eterm 0.9.3 and am having a problem with selection
> behavior. My windows Manager is KDE 3.4 and I am launching
> Eterm with the foolowing swithceds
>
> Eterm -f white --select-line=off --xterm-select=on
>
> Bott
