unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: "Kiên Nguyễn Quang" <kien.n.quang@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 57386@debbugs.gnu.org
Subject: bug#57386: 29.0.50; support make-symbolic-link without admin priviledge on Windows
Date: Thu, 25 Aug 2022 18:51:30 +0900	[thread overview]
Message-ID: <CAL7sU5i8pFP3UvWWsoUEk81nYaXn-Z-KBWurMGRVFeKtCg2AJA@mail.gmail.com> (raw)
In-Reply-To: <83y1vc3d1l.fsf@gnu.org>


[-- Attachment #1.1: Type: text/plain, Size: 1140 bytes --]

>
>
>  (is anyone who has Windows 10 still likely to
> use those old releases, given the automatic updates in Windows 10 that
> cannot be turned off? and if they do, do they indeed get
> ERROR_INVALID_PARAMETER?)
>
There is LTS branch of Windows that gets updated regularly and doesn't have
to update to a newer release build.
Those users (mostly enterprise users/devs) will get the
ERROR_INVALID_PARAMETER, I've tested that.

> When you call an API with a parameter that is invalid, you are risking
> an exception, depending on the API and the build (debug or not).  This
> has various unpleasant consequences; in the worst case, the Emacs
> process could be terminated.  As documented, the problem is limited to
> CRT functions, but our general policy is to avoid that even when using
> the Win32 APIs.  And version check is a simple enough way of avoiding
> that, so I see no reason not to do it here.

Okay, that makes sense. Although I think that's the problem of CRT APIs
only, as API should never throw exceptions, which is a foreign concept to
ABI and requires an exact library match to handle correctly

The new patch is attached.

[-- Attachment #1.2: Type: text/html, Size: 1563 bytes --]

[-- Attachment #2: 0002-Make-native-comp-debug-0-for-Windows.patch --]
[-- Type: application/octet-stream, Size: 879 bytes --]

From 8ab79a8b30cb55c7a41fe48bc7a6002bb62be44d Mon Sep 17 00:00:00 2001
From: Kien Nguyen <kien.n.quang@gmail.com>
Date: Sat, 15 May 2021 10:57:25 +0900
Subject: [PATCH] Make native-comp-debug 0 for Windows

* lisp/emacs-lisp/comp.el (native-comp-debug): dont make debug native-comp for Windows

---
 lisp/emacs-lisp/comp.el | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/lisp/emacs-lisp/comp.el b/lisp/emacs-lisp/comp.el
index 3e7f17ef1c..85d0cea212 100644
--- a/lisp/emacs-lisp/comp.el
+++ b/lisp/emacs-lisp/comp.el
@@ -55,7 +55,7 @@ native-comp-speed
   :safe #'integerp
   :version "28.1")
 
-(defcustom native-comp-debug (if (eq 'windows-nt system-type) 1 0)
+(defcustom native-comp-debug 0
   "Debug level for native compilation, a number between 0 and 3.
 This is intended for debugging the compiler itself.
   0 no debug output.
-- 
2.31.1.windows.1


  reply	other threads:[~2022-08-25  9:51 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-24 15:33 bug#57386: 29.0.50; support make-symbolic-link without admin priviledge on Windows Kiên Nguyễn Quang
2022-08-24 16:00 ` Eli Zaretskii
2022-08-24 18:05   ` Kiên Nguyễn Quang
2022-08-24 18:26     ` Eli Zaretskii
2022-08-25  1:30       ` Kiên Nguyễn Quang
2022-08-25  5:50         ` Eli Zaretskii
2022-08-25  8:52           ` Kiên Nguyễn Quang
2022-08-25  9:09             ` Eli Zaretskii
2022-08-25  9:51               ` Kiên Nguyễn Quang [this message]
2022-08-25  9:57                 ` Eli Zaretskii
2022-08-25 10:32                   ` Kiên Nguyễn Quang
2022-08-25 13:22                     ` Eli Zaretskii
2022-08-25 11:35                 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-08-25 12:59                   ` 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

  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=CAL7sU5i8pFP3UvWWsoUEk81nYaXn-Z-KBWurMGRVFeKtCg2AJA@mail.gmail.com \
    --to=kien.n.quang@gmail.com \
    --cc=57386@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).