unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Thien-Thi Nguyen <ttn@gnu.org>
To: emacs-devel@gnu.org
Subject: Re: [elpa] master a179572 3/4: [admin] Specify bash in update-archive.sh shebang line.
Date: Tue, 28 Feb 2017 17:29:01 +0100	[thread overview]
Message-ID: <87innucm9e.fsf@zigzag.favinet> (raw)
In-Reply-To: <874lze60rl.fsf@linux-m68k.org> (Andreas Schwab's message of "Tue, 28 Feb 2017 11:57:34 +0100")

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


() Andreas Schwab <schwab@linux-m68k.org>
() Tue, 28 Feb 2017 11:57:34 +0100

   See [link].  The linebreak before function_body represents
   _optional_ newlines.

Thanks for the link.  I see that the ‘linebreak’ production:

 linebreak        : newline_list
                  | /* empty */
                  ;

includes possibility of expanding to nothing, and wonder (idly)
if that was always the case.  Somehow i have the impression its
optionality is "new".

-- 
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:[~2017-02-28 16:29 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20170228044932.27875.86801@vcs0.savannah.gnu.org>
     [not found] ` <20170228044933.97CDF25FCA@vcs0.savannah.gnu.org>
2017-02-28  5:37   ` [elpa] master a179572 3/4: [admin] Specify bash in update-archive.sh shebang line Stefan Monnier
2017-02-28  5:52     ` Thien-Thi Nguyen
2017-02-28  7:22       ` Stefan Monnier
2017-02-28 10:09         ` Thien-Thi Nguyen
2017-02-28 10:57           ` Andreas Schwab
2017-02-28 16:29             ` Thien-Thi Nguyen [this message]
2017-02-28 17:33               ` Stefan Monnier

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=87innucm9e.fsf@zigzag.favinet \
    --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).