all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Manuel Giraud <manuel@ledu-giraud.fr>
Cc: luangruo@yahoo.com, 58406@debbugs.gnu.org, manuel@ledu-giraud.fr
Subject: bug#58406: 29.0.50; Bars refactoring?
Date: Mon, 10 Oct 2022 11:58:24 +0300	[thread overview]
Message-ID: <83r0zggimn.fsf@gnu.org> (raw)
In-Reply-To: <87tu4cyszl.fsf@elite.giraud> (message from Manuel Giraud on Mon,  10 Oct 2022 10:37:18 +0200)

> Cc: 58406@debbugs.gnu.org, Manuel Giraud <manuel@ledu-giraud.fr>
> From: Manuel Giraud <manuel@ledu-giraud.fr>
> Date: Mon, 10 Oct 2022 10:37:18 +0200
> 
> > Why ENUM_BF?
> 
> A mistake.  I thought it was the way to use enum types in emacs.

Only for bitfields in a struct.





  parent reply	other threads:[~2022-10-10  8:58 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-10  7:37 bug#58406: 29.0.50; Bars refactoring? Manuel Giraud
2022-10-10  8:08 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-10-10  8:37   ` Manuel Giraud
2022-10-10  8:51     ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-10-10  9:01       ` Eli Zaretskii
2022-10-10 10:05         ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-10-10 11:24           ` Eli Zaretskii
2022-10-10 13:42             ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-10-10 12:10       ` Manuel Giraud
2022-10-10 13:41         ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-10-10 14:30           ` Manuel Giraud
2022-10-10 16:08             ` Eli Zaretskii
2022-10-11  0:32             ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-10-10  8:58     ` Eli Zaretskii [this message]
2022-10-10  8:45 ` Eli Zaretskii
2022-10-10 11:58   ` Manuel Giraud

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=83r0zggimn.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=58406@debbugs.gnu.org \
    --cc=luangruo@yahoo.com \
    --cc=manuel@ledu-giraud.fr \
    /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.