On Thu, Nov 02, 2006 at 07:05:34PM +0100, Jan Gorski wrote:
> > Or perhaps the xinerama configuration limits the amount of X resource data
> > that is stored, to allow for multiple screens.
>
> Well, I looked for xinerama bugs, and voila
>
> https://bugs.freedesktop.org/show_bug.cgi?id=3040
>
>
On Thu, Nov 02, 2006 at 01:55:41PM +0100, Jan Gorski wrote:
> On Wed, 01 Nov 2006 at 19:51:20 -0500, Thomas Dickey wrote:
> > You could add a printf to get the number of screens in the display,
> > e.g., I did this (enabling trace), but a printf would also work:
> >
> > Trace("FIXME %d\n", dpy
On Wed, 01 Nov 2006 at 19:51:20 -0500, Thomas Dickey wrote:
> You could add a printf to get the number of screens in the display,
> e.g., I did this (enabling trace), but a printf would also work:
>
> Trace("FIXME %d\n", dpy->default_screen);
> Trace("FIXME %d\n", dpy->nscreens);
> if
On Thu, Nov 02, 2006 at 12:44:03AM +0100, Jan Gorski wrote:
> On Mon, 30 Oct 2006 at 18:50:46 -0500, Thomas Dickey wrote:
> > If you could reproduce it with a copy of xterm built with debug code,
> > then it's possible that you could attach it with gdb from another window
> > and see where it's han
On Mon, 30 Oct 2006 at 18:50:46 -0500, Thomas Dickey wrote:
> If you could reproduce it with a copy of xterm built with debug code,
> then it's possible that you could attach it with gdb from another window
> and see where it's hanging. You wouldn't need the setgid mode on the
> executable, since
On Tue, Oct 31, 2006 at 12:21:35AM +0100, Jan Gorski wrote:
> On Sun, 25 Sep 2005 at 12:32:07 -0400, Thomas Dickey wrote:
> > On Sun, Sep 25, 2005 at 04:50:14PM +0200, Jan Gorski wrote:
> > > On Sat, 24 Sep 2005 at 19:25:52 -0400, Thomas Dickey wrote:
> > > > (That would be "configure --enable-trac
On Sun, 25 Sep 2005 at 12:32:07 -0400, Thomas Dickey wrote:
> On Sun, Sep 25, 2005 at 04:50:14PM +0200, Jan Gorski wrote:
> > On Sat, 24 Sep 2005 at 19:25:52 -0400, Thomas Dickey wrote:
> > > (That would be "configure --enable-trace --enable-wide-chars
> > > --enable-luit",
> > > and the executabl
On Sun, Sep 25, 2005 at 04:50:14PM +0200, Jan Gorski wrote:
> On Sat, 24 Sep 2005 at 19:25:52 -0400, Thomas Dickey wrote:
> > (That would be "configure --enable-trace --enable-wide-chars --enable-luit",
> > and the executable produces Trace-parent.out and Trace-child.out)
>
> Well, I've run it. Tr
On Sat, 24 Sep 2005 at 19:25:52 -0400, Thomas Dickey wrote:
> (That would be "configure --enable-trace --enable-wide-chars --enable-luit",
> and the executable produces Trace-parent.out and Trace-child.out)
Well, I've run it. Traces are in http://slimak.info/~slimak/traces.tar.bz2 if
you want to l
On Sun, Sep 25, 2005 at 12:40:03AM +0200, Jan Gorski wrote:
> On Sat, 24 Sep 2005 at 15:21:54 -0400, Thomas Dickey wrote:
> > If you can kill the mc process from another xterm without killing the xterm,
> > it is likely that the problem lies in mc rather than xterm.
>
> I can kill mc, but xterm is
On Sat, 24 Sep 2005 at 15:21:54 -0400, Thomas Dickey wrote:
> If you can kill the mc process from another xterm without killing the xterm,
> it is likely that the problem lies in mc rather than xterm.
I can kill mc, but xterm is still frozen. Similar thing happens with mutt. BTW,
is it possible an
On Sat, Sep 24, 2005 at 12:20:05PM +0200, Jan Gorski wrote:
> Package: xterm
> Version: 6.8.2.dfsg.1-7
> Severity: normal
>
>
> I've recently set LC_CTYPE to pl_PL.UTF-8. Now after starting X first and
> second
> run of mc in xterm is unsuccesfull.
>
> Run 1. Only first line (menubar) is rende
Package: xterm
Version: 6.8.2.dfsg.1-7
Severity: normal
I've recently set LC_CTYPE to pl_PL.UTF-8. Now after starting X first and second
run of mc in xterm is unsuccesfull.
Run 1. Only first line (menubar) is renderd.
Run 2. First line and 39 characters of second line are visible.
Run 3. Not al
13 matches
Mail list logo
