all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Richard Stallman <rms@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 30005@debbugs.gnu.org, p.stephani2@gmail.com
Subject: bug#30005: 27.0.50; call-interactively doesn't work correctly if the interactive specification has an embedded null byte
Date: Tue, 23 Jan 2018 13:06:35 -0500	[thread overview]
Message-ID: <E1ee2xv-0006ay-Pa@fencepost.gnu.org> (raw)
In-Reply-To: <83shawzi0y.fsf@gnu.org> (message from Eli Zaretskii on Tue, 23 Jan 2018 17:55:41 +0200)

[[[ To any NSA and FBI agents reading my email: please consider    ]]]
[[[ whether defending the US Constitution against all enemies,     ]]]
[[[ foreign or domestic, requires you to follow Snowden's example. ]]]

  > That's not my understanding of the preferred style.  My understanding,
  > and what I do in practice, is that variables used only in a small
  > portion of a function should be declared before the use, so that all
  > the references to those variables are localized to the fragment where
  > they are used.  By contrast, in this case these variables are used all
  > over the function, so it makes much less sense to delay their
  > declaration.

I agree.

-- 
Dr Richard Stallman
President, Free Software Foundation (https://gnu.org, https://fsf.org)
Internet Hall-of-Famer (https://internethalloffame.org)
Skype: No way! See https://stallman.org/skype.html.






  reply	other threads:[~2018-01-23 18:06 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-06 11:39 bug#30005: 27.0.50; call-interactively doesn't work correctly if the interactive specification has an embedded null byte Philipp
2018-01-20 12:02 ` Eli Zaretskii
2018-01-22 22:25   ` Philipp Stephani
2018-01-23 15:55     ` Eli Zaretskii
2018-01-23 18:06       ` Richard Stallman [this message]
2018-02-03 21:48       ` 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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=E1ee2xv-0006ay-Pa@fencepost.gnu.org \
    --to=rms@gnu.org \
    --cc=30005@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    --cc=p.stephani2@gmail.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.