From: Robert Pluim <rpluim@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Po Lu <luangruo@yahoo.com>, John t <jturner.usa@gmail.com>,
65048@debbugs.gnu.org
Subject: bug#65048: 29.1; cli argument "-x" fails with "unknown option" error on PGTK Emacs
Date: Wed, 09 Aug 2023 19:34:34 +0200 [thread overview]
Message-ID: <87v8do6rx1.fsf@gmail.com> (raw)
In-Reply-To: <838rakmodj.fsf@gnu.org> (Eli Zaretskii's message of "Wed, 09 Aug 2023 14:44:24 +0300")
>>>>> On Wed, 09 Aug 2023 14:44:24 +0300, Eli Zaretskii <eliz@gnu.org> said:
>> From: John t <jturner.usa@gmail.com>
>> Date: Tue, 8 Aug 2023 23:51:32 -0400
>>
Eli> (You've replied only to me, so no one else saw your message. Please
Eli> in the future use Reply All, to keep the bug address on the CC list.)
>> I have tested the patch with PGTK, and headless configurations and the option seems to work
>> correctly.
>>
>> A friend with an x11 emacs tested the patch and reported that it returned the "unknown option" error.
Eli> That's strange. Can someone please test the patch on X and see if it
Eli> works, and if not, tell me where I goofed?
Looks ok to me:
$ src/emacs -x
Wrong type argument: stringp, nil
Error: wrong-type-argument (stringp nil)
mapbacktrace(#f(compiled-function (evald func args flags) #<bytecode -0x1d4598e800517817>))
debug-early-backtrace()
debug-early(error (wrong-type-argument stringp nil))
string-match("^///+" nil)
command-line-normalize-file-name(nil)
command-line-1(("-scripteval"))
command-line()
normal-top-level()
Robert
--
next prev parent reply other threads:[~2023-08-09 17:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-04 2:47 bug#65048: 29.1; cli argument "-x" fails with "unknown option" error on PGTK Emacs John t
2023-08-04 6:20 ` Eli Zaretskii
[not found] ` <CAJ2jvP+Opyt7XEtoZsTGKw0M-D-Ws1D5eFRi+81gz5z3S7FR6Q@mail.gmail.com>
2023-08-09 11:44 ` Eli Zaretskii
2023-08-09 17:34 ` Robert Pluim [this message]
2023-08-09 18:05 ` Eli Zaretskii
2023-08-10 7:37 ` Robert Pluim
2023-08-10 7:51 ` Eli Zaretskii
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=87v8do6rx1.fsf@gmail.com \
--to=rpluim@gmail.com \
--cc=65048@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=jturner.usa@gmail.com \
--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 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.