From: Alex Branham <alex.branham@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 31148@debbugs.gnu.org
Subject: bug#31148: 26.1; require w32 errors
Date: Fri, 13 Apr 2018 12:58:46 -0500 [thread overview]
Message-ID: <87a7u7ng2x.fsf@gmail.com> (raw)
In-Reply-To: <834lkf56vm.fsf@gnu.org>
On Fri 13 Apr 2018 at 12:54, Eli Zaretskii <eliz@gnu.org> wrote:
>> From: Alex Branham <alex.branham@gmail.com>
>> Cc: 31148@debbugs.gnu.org
>> Date: Fri, 13 Apr 2018 12:45:37 -0500
>>
>> (if (not (w32-shell-dos-semantics))
>> (add-hook 'comint-output-filter-functions 'ess-bugs-exit-notify-sh))
>>
>> Which causes errors on non-windows machines unless you wrap the call to
>> w32-shell-dos-semantics in (and (fboundp ...)), which looks weird to me:
>>
>> (if (not (and
>> (fboundp 'w32-shell-dos-semantics)
>> (w32-shell-dos-semantics)))
>> (add-hook 'comint-output-filter-functions 'ess-bugs-exit-notify-sh))
>>
>> They also have code like:
>>
>> (if (ess-microsoft-p)
>> (w32-short-file-name ...))
>>
>> which causes byte compiler warnings about w32 being undefined. I guess
>> the best/only way to get rid of these is to (declare-function ... ),
>> right?
>
> Yes, declare-function should solve at least some of those.
>
> As for the rest, I suggest to define a variable/function (seems like
> ess-microsoft-p is already doing that) to tell you whether you are on
> MS-Windows, e.g., by looking at system-type, and then condition all
> the calls to w32-specific functions on that variable/function.
Thanks, will do. I guess this bug report can be closed (can I do that myself?)
Thanks again,
Alex
next prev parent reply other threads:[~2018-04-13 17:58 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-13 14:50 bug#31148: 26.1; require w32 errors Alex Branham
2018-04-13 15:13 ` Eli Zaretskii
2018-04-13 15:15 ` Alex Branham
2018-04-13 17:22 ` Eli Zaretskii
2018-04-13 17:45 ` Alex Branham
2018-04-13 17:54 ` Eli Zaretskii
2018-04-13 17:58 ` Alex Branham [this message]
2018-04-13 18:58 ` Eli Zaretskii
2018-04-13 19:04 ` bug#31148: Close Alex Branham
2018-04-14 4:22 ` bug#31148: 26.1; require w32 errors Noam Postavsky
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=87a7u7ng2x.fsf@gmail.com \
--to=alex.branham@gmail.com \
--cc=31148@debbugs.gnu.org \
--cc=eliz@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).