unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Thien-Thi Nguyen <ttn@gnu.org>
To: emacs-devel <emacs-devel@gnu.org>
Subject: Re: A couple of things that I think should be in byte bytecode meta comments
Date: Sat, 13 Jan 2018 20:44:52 +0100	[thread overview]
Message-ID: <87y3l1lf0r.fsf@gnuvola.org> (raw)
In-Reply-To: <CANCp2gZAcr_L9UKPb5snbP4ei0O_Av26OTk0m6+4mapvFUTvvA@mail.gmail.com> (Rocky Bernstein's message of "Sat, 23 Dec 2017 21:44:34 -0500")

[-- Attachment #1: Type: text/plain, Size: 1295 bytes --]


() Rocky Bernstein <rocky@gnu.org>
() Sat, 23 Dec 2017 21:44:34 -0500

   Because Emacs is critically used, by necessity the
   overwhelming and more vocal group is in the "why?" the camp.
   There are other venues that have the luxury to be more in the
   "why not?" camp for things like this.

I think many people are also trying to relate to you as a fellow
hacker, on a "what could possibly go wrong" level, w/ varying
bits of experience and familiarity (or lack thereof) of Emacs
conventions, that inform their instincts.

Personally, i think the ‘load’ conventions are well-entrenched
and so there is no real need to embed filename (can be reliably
inferred for "normal" usage -- people wandering into the muck
probably know what they're after, anyway, and can make do).

An argument explicitly against embedding absolute filename would
be the recent trend towards reproducible builds.  Everyone is
trying to catch up to Emacs' historical ignorance^Wbliss.  :-D

-- 
Thien-Thi Nguyen -----------------------------------------------
 (defun responsep (query)
   (pcase (context query)
     (`(technical ,ml) (correctp ml))
     ...))                              748E A0E8 1CB8 A748 9BFA
--------------------------------------- 6CE4 6703 2224 4C80 7502


[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 197 bytes --]

  reply	other threads:[~2018-01-13 19:44 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-22 17:54 A couple of things that I think should be in byte bytecode meta comments Rocky Bernstein
2017-12-22 17:55 ` Rocky Bernstein
2017-12-22 18:30   ` Eli Zaretskii
2017-12-22 18:49     ` Rocky Bernstein
2017-12-22 20:25       ` Eli Zaretskii
2017-12-22 20:55         ` Rocky Bernstein
2017-12-23  8:25           ` Eli Zaretskii
2017-12-23  8:44             ` Rocky Bernstein
2017-12-23 15:32               ` Robert Weiner
2017-12-23 17:16                 ` Rocky Bernstein
2017-12-23 18:30                   ` Robert Weiner
2017-12-24  2:44                     ` Rocky Bernstein
2018-01-13 19:44                       ` Thien-Thi Nguyen [this message]
2017-12-22 21:27 ` Andreas Schwab
2017-12-22 21:43   ` Rocky Bernstein
2017-12-23  8:25     ` Andreas Schwab
2017-12-23  8:35       ` Rocky Bernstein

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=87y3l1lf0r.fsf@gnuvola.org \
    --to=ttn@gnu.org \
    --cc=emacs-devel@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).