From: Chris Leyon <cleyon@gmail.com>
To: Paul Eggert <eggert@cs.ucla.edu>
Cc: Chong Yidong <cyd@gnu.org>, 10677@debbugs.gnu.org
Subject: bug#10677: [Chris Leyon] Re: bug#10677: 24.0.93; missing pathmax.h on Solaris
Date: Sat, 3 Mar 2012 12:07:47 -0500 [thread overview]
Message-ID: <CALfY4+-eaBgVWrEAx_PeTnyxAgk-xN+V+NGv=OV1iwfDBHxL+w@mail.gmail.com> (raw)
In-Reply-To: <4F519022.6090608@cs.ucla.edu>
On Fri, Mar 2, 2012 at 22:29, Paul Eggert <eggert@cs.ucla.edu> wrote:
> Thanks for diagnosing the problem. The ncurses 'configure' stuff
> changed recently, and it continues to be a mess (with comments
> indicating that it's a mess, sigh) [...]
Paul, your patch to configure.in worked on Solaris. The new configure
script detected -ltermcap for tputs, ncurses was not referenced at all
on the linklines, and the pointer sizes were successfully detected.
There were no errors encountered during compilation (there were some
warnings, of course), but an executable was created which runs fine.
Thanks for all your help in fixing this problem.
And now I would like to report an incompatible change to the Lisp
reader which I did not see documented in etc/NEWS but might be worth
mentioning (or fixing). In Emacs 23, the following syntax for
specifying the key C-, is accepted:
(global-set-key [(control ,)] 'my-command)
In Emacs 24, this generates an error: "Invalid read syntax: )"
next prev parent reply other threads:[~2012-03-03 17:07 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-31 7:17 bug#10677: 24.0.93; missing pathmax.h on Solaris Chong Yidong
2012-02-01 6:10 ` Paul Eggert
2012-02-02 1:49 ` bug#10677: [Chris Leyon] " Chong Yidong
2012-02-02 4:52 ` Paul Eggert
2012-02-05 23:22 ` Chris Leyon
2012-02-27 9:05 ` Chong Yidong
2012-03-02 22:34 ` Chris Leyon
2012-03-03 3:29 ` Paul Eggert
2012-03-03 17:07 ` Chris Leyon [this message]
2012-03-04 2:58 ` Paul Eggert
2012-03-04 9:48 ` Chong Yidong
2012-03-04 18:10 ` Paul Eggert
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CALfY4+-eaBgVWrEAx_PeTnyxAgk-xN+V+NGv=OV1iwfDBHxL+w@mail.gmail.com' \
--to=cleyon@gmail.com \
--cc=10677@debbugs.gnu.org \
--cc=cyd@gnu.org \
--cc=eggert@cs.ucla.edu \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.