From: Joe Trivers via help-gnu-emacs <help-gnu-emacs@gnu.org>
To: <help-gnu-emacs@gnu.org>
Subject: Re: emacs won't start interactively
Date: Tue, 28 May 2019 17:30:11 +0000 [thread overview]
Message-ID: <BN6P102MB0066018E035EE9803CF67599EE1E0@BN6P102MB0066.NAMP102.PROD.OUTLOOK.COM> (raw)
From: help-gnu-emacs On Behalf Of Eli Zaretskii
Sent: 28 May, 2019 10:48 AM
>> Date: Tue, 28 May 2019 01:09:23 +0000
>> From: Joe Trivers via help-gnu-emacs <help-gnu-emacs@gnu.org>
>>
>> Any further thoughts about what might be happening here? And on how gdb could be making it work correctly?
>
> I'd have a good look at the environment variables you have set. Are
> some of them Emacs related, perhaps? Any suspicious ones? Maybe post
> the whole list of them here, perhaps someone will spot something.
Nothing looks relevant, other than PATH. Is there a way in cmd.exe (like env in bash) to get such a list?
> Also, do you see anything in the Windows' Event Logger, under
> Application, around the times when you start Emacs and it immediately
> exits?
You may have something there.
Log Name: Application
Source: CbDefense
Information: The application "C:\gnu\emacs-26.1\bin\emacs-26.1.exe" attempted to inject code into the process "C:\GNU\emacs-26.1\bin\emacs-26.1.exe" by calling the function "SetWindowsHookExA". The operation was blocked and the application terminated by Confer.
CbDefense is Carbon Black Antivirus, mandated by our IT department. It also runs on the laptop where emacs 26.1 works properly. Perhaps there's a way to whitelist emacs?
Incidentally, when I typed the command into the Windows command prompt I used capital letters for "GNU".
HAH! I renamed the C:\GNU directory to C:\gnu (in lower case) and now it works properly. Maybe CbDefense lowercases one string but not the other?
And, yes, the "gnu" directory name is in lower case on the laptop where emacs has been working since last year. [facepalm]
Thanks for all your help. Who'd'a thunk it? /Joe
The content of this message is APPLIED MATERIALS CONFIDENTIAL. If you are not the intended recipient, please notify me, delete this email and do not use or distribute this email.
next reply other threads:[~2019-05-28 17:30 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-28 17:30 Joe Trivers via help-gnu-emacs [this message]
2019-05-28 18:55 ` emacs won't start interactively Eli Zaretskii
-- strict thread matches above, loose matches on Subject: below --
2019-05-28 1:09 Joe Trivers via help-gnu-emacs
2019-05-28 2:10 ` Óscar Fuentes
2019-05-28 14:51 ` Eli Zaretskii
2019-05-28 14:48 ` Eli Zaretskii
[not found] <BN6P102MB00661ACF5A35AD540DAC0C10EE1D0@BN6P102MB0066.NAMP102.PROD.OUTLOOK.COM>
2019-05-27 16:59 ` Eli Zaretskii
2019-05-27 17:09 ` Óscar Fuentes
2019-05-26 3:27 Joe_Trivers--- via help-gnu-emacs
2019-05-26 13:43 ` Óscar Fuentes
2019-05-26 14:41 ` 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=BN6P102MB0066018E035EE9803CF67599EE1E0@BN6P102MB0066.NAMP102.PROD.OUTLOOK.COM \
--to=help-gnu-emacs@gnu.org \
--cc=Joe_Trivers@amat.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.