From: David Kastrup <dak@gnu.org>
Cc: Andreas Schwab <schwab@suse.de>, emacs-devel@gnu.org
Subject: Re: Updated multi-tty support for Emacs
Date: 03 Jan 2004 13:52:46 +0100 [thread overview]
Message-ID: <x5hdzdyz1d.fsf@lola.goethe.zz> (raw)
In-Reply-To: <lorentey.g.e.devel.87d6a1gyjl.elte@eris.elte.hu>
lorentey@elte.hu (Lőrentey Károly) writes:
> Andreas Schwab <schwab@suse.de> writes:
> > lorentey@elte.hu (Károly Lőrentey) writes:
> >
> >> Please let me know what you think about this project. I badly need
> >> testers, so if you think this would be useful for you, please give it
> >> a try and tell me your results. (Note that Mac, MSDOS and Windows
> >> support is broken at the moment, and I will probably need some help
> >> with these ports later.)
> >
> > Also it won't build on any non-glibc system, due the unconditional use
> > of getpt() in emacsclient.
>
> I fixed this by eliminating the pty-proxy kludge from emacsclient.
> patch-35 compiles and runs fine on Solaris with GCC. (I suspect I
> may have inadvertently used some GCC extensions (conditional
> lvalues) -- tell me if you succeed to compile the branch with
> another compiler.)
Conditional lvalues _are_ a GNU extension. You can work around by
saying something like
*(condition ? &a : &b) = ...
but it will in general be better just to write
if (condition)
a = ...;
else
b = ...;
Even if a stupid compiler does not catch the code duplication, only
one branch gets executed, anyway.
--
David Kastrup, Kriemhildstr. 15, 44793 Bochum
next prev parent reply other threads:[~2004-01-03 12:52 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-02 12:59 Updated multi-tty support for Emacs Károly Lőrentey
2004-01-02 21:12 ` Andreas Schwab
2004-01-03 9:40 ` Lőrentey Károly
2004-01-03 12:52 ` David Kastrup [this message]
2004-01-03 17:13 ` Lőrentey Károly
2004-01-03 18:49 ` David Kastrup
2004-01-04 22:04 ` Andreas Schwab
2004-01-08 18:39 ` Lőrentey Károly
2004-01-11 0:19 ` Lőrentey Károly
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=x5hdzdyz1d.fsf@lola.goethe.zz \
--to=dak@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=schwab@suse.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).