From: Noam Postavsky <npostavs@gmail.com>
To: rocky <rocky@gnu.org>
Cc: Emacs developers <Emacs-devel@gnu.org>
Subject: Re: Should wide-int be registered in features?
Date: Thu, 5 Apr 2018 18:41:14 -0400 [thread overview]
Message-ID: <CAM-tV-8=-_BpZfFinwhw1ARx0z_-96yCP=9wRsJW+O=_k0LK0w@mail.gmail.com> (raw)
In-Reply-To: <1522967667743-0.post@n8.nabble.com>
On 5 April 2018 at 18:34, rocky <rocky@gnu.org> wrote:
> and how inside of Emacs is one supposed to know if this is in effect?
You can check `system-configuration-options'.
next prev parent reply other threads:[~2018-04-05 22:41 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-05 22:12 Should wide-int be registered in features? Rocky Bernstein
2018-04-05 22:21 ` Stefan Monnier
2018-04-05 22:34 ` rocky
2018-04-05 22:41 ` Noam Postavsky [this message]
2018-04-05 22:46 ` rocky
2018-04-06 0:56 ` Stefan Monnier
2018-04-06 6:28 ` Andreas Schwab
2018-04-06 6:30 ` Ulrich Mueller
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='CAM-tV-8=-_BpZfFinwhw1ARx0z_-96yCP=9wRsJW+O=_k0LK0w@mail.gmail.com' \
--to=npostavs@gmail.com \
--cc=Emacs-devel@gnu.org \
--cc=rocky@gnu.org \
/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).