Re: NeedFunctionPrototypes and ANSI C
On Wed, 13 Aug 2003, Mark Vojkovich wrote:
On Wed, 13 Aug 2003, Warren Turkal wrote:
Is there an effort to get rid of NeedFunctionPrototypes and to convert
function prototypes to ANSI style? If so, I would like to work on doing
this for the xwininfo binary.
I change them whenever I'm working in particular parts of the
tree that haven't been converted yet, and so do a few other people.
I think we avoid wholesale changes across the board because of
the risk it imposes. There have been some breakages when people
didn't pay enough attention and had the arguments reversed. eg:
int func(y, x)
int x;
int y;
{
/* watch out! */
}
Comparing binaries addresses this (except of course where an ifdef
confuses the issue). Even with that, I recall two instances where I
made an error (caught by other people).
So piecemeal changes seem safer. People tend to go on autopilot
when making too many changes of this type in one sitting and have a tendency
to break the case above. You can also introduce some promotion problems
if you're not careful.
That, and changing things incompatibly (putting 'void' on prototypes where
the old headers don't specify).
--
T.E.Dickey [EMAIL PROTECTED]
http://invisible-island.net
ftp://invisible-island.net
___
Devel mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/devel
Re: NeedFunctionPrototypes and ANSI C
On Wed, 13 Aug 2003, Warren Turkal wrote: Is there an effort to get rid of NeedFunctionPrototypes and to convert function prototypes to ANSI style? If so, I would like to work on doing this for the xwininfo binary. People do work on this occasionally. I've made some notes here: http://dickey.his.com/ansification/index.html My research indicates that X11R6.3+ require an ANSI compiler and that this type of conversion is desirable. Warren Turkal -- T.E.Dickey [EMAIL PROTECTED] http://invisible-island.net ftp://invisible-island.net ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
Re: CVS Update: xc (branch: trunk)
On Wed, 30 Jul 2003, Harold L Hunt II wrote: Todd T. Fries wrote: Penned by Daniel Stone on Wed, Jul 30, 2003 at 04:51:49PM +1000, we have: [..] | I did suggest this (mv hp,v hp.old,v). If you guys care about history at all, aka the ability to checkout files in the past, you would not suggest nor impement this suggestion. Does history matter when some people simply cannot checkout a tag set because of a mistake that was made? The balanced response here is that the history is not as important as making sure that all developers can move forward. Of course, we do this only in rare circumstances, but this is one of them. I fetch older versions all the time - on xfree86, I did that, for instance to narrow down the range of dates for a bug introduced into the mouse driver. Having a known working version of something lets you cut down on the effort to isolate a bug. (Moving forward doesn't use the archives for anything except an odd backup format). -- T.E.Dickey [EMAIL PROTECTED] http://invisible-island.net ftp://invisible-island.net ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
[XFree86] Re: XTerm OpenSSH question w/ freezing.
On Thu, 10 Jul 2003, war wrote: Sometimes when I use openssh (latest) and do find . or ls -lR /dev or similiar, my xterm 'freezes up', there is no way to fix it but to kill the xterm usually. what version of xterm? The only issue that comes to mind is the fix for blinking cursor a few months ago. This NEVER occurs in telnet. The error is completely reproducable when you come across it. ie: one may just be browsing the filesystem and when you come across this problem, you can launch another xterm and the EXACT same thing happens when you try to do it again Bug reports on similiar issues seem to be sparse and people I know never seem to have the problem, perhaps they use ssh from a windows machine. I was wondering what causes this, and is there a way to fix it? -- T.E.Dickey [EMAIL PROTECTED] http://invisible-island.net ftp://invisible-island.net ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
[XFree86] Re: XTerm OpenSSH question w/ freezing.
On Thu, 10 Jul 2003, war wrote: Any version, currently using the latest stable, xterm-179. There was a Debian bug report last week in this area, but it turned out to be a bug in bash (I don't know more than that). On Thu, 10 Jul 2003, Thomas E. Dickey wrote: On Thu, 10 Jul 2003, war wrote: Sometimes when I use openssh (latest) and do find . or ls -lR /dev or similiar, my xterm 'freezes up', there is no way to fix it but to kill the xterm usually. what version of xterm? The only issue that comes to mind is the fix for blinking cursor a few months ago. This NEVER occurs in telnet. The error is completely reproducable when you come across it. ie: one may just be browsing the filesystem and when you come across this problem, you can launch another xterm and the EXACT same thing happens when you try to do it again Bug reports on similiar issues seem to be sparse and people I know never seem to have the problem, perhaps they use ssh from a windows machine. I was wondering what causes this, and is there a way to fix it? -- T.E.Dickey [EMAIL PROTECTED] http://invisible-island.net ftp://invisible-island.net -- T.E.Dickey [EMAIL PROTECTED] http://invisible-island.net ftp://invisible-island.net ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
[XFree86] Re: XTerm OpenSSH question w/ freezing.
On Thu, 10 Jul 2003, war wrote: Ok, next time I can reproduce this problem I will try csh/ksh other shells and see, thanks for the insight. no problem (it may be the same problem, or one that I haven't read about). On Thu, 10 Jul 2003, Thomas E. Dickey wrote: On Thu, 10 Jul 2003, war wrote: Any version, currently using the latest stable, xterm-179. There was a Debian bug report last week in this area, but it turned out to be a bug in bash (I don't know more than that). On Thu, 10 Jul 2003, Thomas E. Dickey wrote: On Thu, 10 Jul 2003, war wrote: Sometimes when I use openssh (latest) and do find . or ls -lR /dev or similiar, my xterm 'freezes up', there is no way to fix it but to kill the xterm usually. what version of xterm? The only issue that comes to mind is the fix for blinking cursor a few months ago. This NEVER occurs in telnet. The error is completely reproducable when you come across it. ie: one may just be browsing the filesystem and when you come across this problem, you can launch another xterm and the EXACT same thing happens when you try to do it again Bug reports on similiar issues seem to be sparse and people I know never seem to have the problem, perhaps they use ssh from a windows machine. I was wondering what causes this, and is there a way to fix it? -- T.E.Dickey [EMAIL PROTECTED] http://invisible-island.net ftp://invisible-island.net -- T.E.Dickey [EMAIL PROTECTED] http://invisible-island.net ftp://invisible-island.net -- T.E.Dickey [EMAIL PROTECTED] http://invisible-island.net ftp://invisible-island.net ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
[XFree86] Re: xterm utmp question
On Tue, 8 Jul 2003, war wrote: Slackware Linux 9.0 on Slackware, utmp is owned by root, so xterm has to be setuid'd to root so it can modify that file: -rws--x--x1 root bin246588 Mar 2 02:52 /usr/X11R6/bin/xterm GCC 3.3 On Tue, 8 Jul 2003, Thomas E. Dickey wrote: On Tue, 8 Jul 2003, war wrote: I build the latest xterm (xterm-179) from http://invisible-island.net/xterm/. With and without --with-utemper option. What type of system? (Linux, Unix, etc). [EMAIL PROTECTED]:~$ w 12:05:27 up 18 min, 1 user, load average: 0.13, 0.54, 0.62 USER TTYLOGIN@ IDLE JCPU PCPU WHAT [EMAIL PROTECTED]:~$ (this is with the one I built) [EMAIL PROTECTED]:~$ /usr/X11R6/bin/xterm [EMAIL PROTECTED]:~$ w 12:05:47 up 19 min, 2 users, load average: 0.30, 0.55, 0.62 USER TTYLOGIN@ IDLE JCPU PCPU WHAT war pts/7 12:050.00s 0.03s 0.01s w [EMAIL PROTECTED]:~$ [EMAIL PROTECTED]:~$ ps auxww|grep xterm|wc 8 1551146 [EMAIL PROTECTED]:~$ How come my xterms do not show up when I type w or who, etc? But using the /usr/X11R6/bin/xterm works fine? -- T.E.Dickey [EMAIL PROTECTED] http://invisible-island.net ftp://invisible-island.net -- T.E.Dickey [EMAIL PROTECTED] http://invisible-island.net ftp://invisible-island.net ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
[XFree86] Re: xterm utmp question
On Tue, 8 Jul 2003, war wrote: Ah, thank you! no problem -- T.E.Dickey [EMAIL PROTECTED] http://invisible-island.net ftp://invisible-island.net ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
Re: xterm can hang, CPU bound
On Mon, 3 Feb 2003, D. Hugh Redelmeier wrote:
| I guess the comparable chunks are like this:
|
| select(6, [4 5], [], NULL, {0, 0}) = 1 (in [4], left {0, 0})
| select(5, [4], [], [], {0, 0}) = 1 (in [4], left {0, 0})
| select(5, [4], [], [], {0, 0}) = 1 (in [4], left {0, 0})
| select(5, [4], [], [], {0, 0}) = 1 (in [4], left {0, 0})
That sure looks like it ought to eat all available CPU.
None of those calls should block.
well - it didn't. I was watching both xload and top. on the redhat8, I
could see that it fell into a pattern that eventually blew up, but not
on the slackware71.
| | What do you think about the approach I suggested (act as if a default
| | CSI...T sequence had been received until the real one is)? Perhaps
| | the default should only be used after some timeout.
| |
| | it's not entirely clear to me what the sequence would be here.
|
| Two obvious ones: the whole xterm region, or an empty region at the
| point of the cursor. I'd vote for the empty region: no information
| about a subsequent click is lost (the answer will be forced to be the
| long form).
|
| Clearly func should be non zero in either case: we don't want to
| cancel the mode.
|
| I do suggest that the default only be installed after a brief timeout.
| How long? A tenth of a second feels about right.
|
| I also suggest that the default be replaced if and when the explicit
| CSI...T sequence is received.
|
| It sounds as if you're proposing to make it return a dummy escape sequence -
| or make the escape sequence terminate automatically after a short time -
| but it's not clear to me
Sorry, I'll try to be clearer.
When a button is pressed in mouse hilite tracking mode,
xterm sends ESC [ M Cb Cx Cy to the PTY
xterm awaits ESC ... T from the PTY, doing nothing else.
The ESC [ Ps ; Ps ; Ps ; Ps ; Ps T informs xterm:
func: non zero to initiate hilite tracking and 0 to abort
startx, starty: starting location for highlighted region
firstrow, lastrow: limits for tracking
I'm proposing that until the ESC ... T message is received from
through the PTY, the xterm should act as if it had received something
like: ESC [ 1 ; curx ; cury ; currow ; currow T
This would be provisional. When (if) an ESC ... T is actually received,
it should override this default.
ok - I can see what you're asking (sounds reasonable).
--
T.E.Dickey [EMAIL PROTECTED]
http://invisible-island.net
ftp://invisible-island.net
___
Devel mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/devel
Re: Fw: Bison/Yacc problems ...
On Wed, 29 Jan 2003, Jamie Risk wrote: I don't know where, but I came across a information about bison version information for compiling XFree86. I'm not hurt that it didn't come from this list, but even an impolite Use bison 1.35: RTFM! would have been useful. byacc is preferable. (the people working on bison appear to have little interest in keeping it compatible with other flavors of yacc) -- T.E.Dickey [EMAIL PROTECTED] http://invisible-island.net ftp://invisible-island.net ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
