From: Peter Mao <peter.mao@gmail.com>
To: Po Lu <luangruo@yahoo.com>
Cc: 65191@debbugs.gnu.org, Eli Zaretskii <eliz@gnu.org>
Subject: bug#65191: 29.1; -ms and -cr CL options don't work
Date: Thu, 10 Aug 2023 23:06:32 -0700 [thread overview]
Message-ID: <CAEK3s1O=cQ9MD11kiYaXFOVw_-OF6EXG6b1rmn_inEyXTmqm9A@mail.gmail.com> (raw)
In-Reply-To: <CAEK3s1OWBRiivB9y7L==y1ue0cQxVujjoWps5Pinbm2NYSTmew@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 243 bytes --]
On Thu, Aug 10, 2023 at 10:43 PM Peter Mao <peter.mao@gmail.com> wrote:
>
> What if you build Emacs without Cairo? Does the problem subside then?
>>
>
> Yes, that fixes the -cr issue!
>
>
But what do I give up by ditching Cairo?
[-- Attachment #2: Type: text/html, Size: 779 bytes --]
next prev parent reply other threads:[~2023-08-11 6:06 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-10 3:00 bug#65191: 29.1; -ms and -cr CL options don't work Peter Mao
2023-08-10 7:01 ` Eli Zaretskii
2023-08-10 7:04 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-08-10 7:19 ` Eli Zaretskii
2023-08-10 7:31 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-08-10 7:47 ` Eli Zaretskii
2023-08-10 7:21 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
[not found] ` <CAEK3s1NrTSTtvQKkhOYaUPafZoSn=Gm=QaYwPO8UUmTC66bUgw@mail.gmail.com>
[not found] ` <CAEK3s1Mtt5jckJzptYdhK4jU5tS0k1SJHXy6DgTGY94CjoYSFQ@mail.gmail.com>
[not found] ` <87il9mqhj1.fsf@yahoo.com>
2023-08-11 5:43 ` Peter Mao
2023-08-11 6:06 ` Peter Mao [this message]
2023-08-11 6:23 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-08-12 4:36 ` Peter Mao
2023-08-12 4:44 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-08-11 6:22 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-08-11 7:24 ` Eli Zaretskii
2023-08-11 7:36 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-08-11 11:05 ` Eli Zaretskii
2023-08-12 0:05 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
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='CAEK3s1O=cQ9MD11kiYaXFOVw_-OF6EXG6b1rmn_inEyXTmqm9A@mail.gmail.com' \
--to=peter.mao@gmail.com \
--cc=65191@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=luangruo@yahoo.com \
/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).