unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Philipp Stephani <p.stephani2@gmail.com>
To: "Vincent Belaïche" <vincent.belaiche@gmail.com>, 27391@debbugs.gnu.org
Subject: bug#27391: 25.2.50; utf-8 coding cookie is not applied on some specific markdown file
Date: Mon, 26 Jun 2017 11:39:12 +0000	[thread overview]
Message-ID: <CAArVCkQmFcwDQ0hzTLuUa1yxNsrYLuGCcHc3MF-be-kMj5p73Q@mail.gmail.com> (raw)
In-Reply-To: <84lgooxnbe.fsf@gmail.com>

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

Vincent Belaïche <vincent.belaiche@gmail.com> schrieb am Mo., 19. Juni 2017
um 12:51 Uhr:

>
> Concerning factorization, couldn't one use [\n\r] in all cases rather
> than a switch based on some input argument ?
>

It should be possible, but it slightly changes the behavior of file-local
variables. I wouldn't expect anything to break though.


>
> I was also wondering whether it is not possible to have a single regexp
> for the whole Local Variable section. The following `doit' function is a
> trial to do so. `M-x doit' will seach forward the whole Local Variables
> section and display "ok" if found, "nak" otherwise.
>
> (defun doit ()
>   (interactive)
>   (let* ((eol "\\(\r\n?\\|\n\\)")
>          (eol-again "\\1")
>          (space-maybe "[ \t]*")
>          ;; suffix may be the empty string
>          (suffix  "\\([^ \r\n]+\\(?:[^\r\n]*[^ \r\n]\\)?\\|\\)")
>          (prefix "\\([ \t]*[^ \r\n]+\\(?:[^\r\n]*[^ \r\n]\\)?\\)")
>          (prefix-again "\\2")
>          (suffix-again "\\3")
>          (symbol: "\\(?:\\(?:[^][()'\" \t\r\n]\\|\\\\[][()'\" \t]\\)+[
> \t]*:\\)")
>          (sexp (concat "\\(?:" (substring prefix 2))))
>
>     (message (if (and (re-search-forward
>                   (concat eol
>                           prefix space-maybe "Local Variables:"
> space-maybe suffix space-maybe eol-again
>                           "\\(?:" prefix space-maybe symbol:  sexp
> space-maybe suffix-again space-maybe eol-again "\\)*"
>                           prefix space-maybe "End:" space-maybe suffix
> space-maybe "\\(" eol-again "\\)?"
>                           )
>                   nil t)
>                   ;; when the tailing eol is not there we must be at EOB.
>                   (or (match-string 3) (eobp)))
>                                     "ok" "nak"))))
>
>
>
Looks good. Consider using `rx' for complex regexes, in my experiences it
increases readability a lot.

[-- Attachment #2: Type: text/html, Size: 2829 bytes --]

  reply	other threads:[~2017-06-26 11:39 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-16 10:00 bug#27391: 25.2.50; utf-8 coding cookie is not applied on some specific markdown file Vincent Belaïche
2017-06-16 12:59 ` Eli Zaretskii
2017-06-16 14:08 ` Vincent Belaïche
2017-06-16 14:10   ` Vincent Belaïche
2017-06-16 18:38   ` Eli Zaretskii
2017-06-16 19:08     ` Vincent Belaïche
2017-06-16 19:15     ` Vincent Belaïche
2017-06-16 19:31       ` Andreas Schwab
2017-06-16 19:37       ` Vincent Belaïche
2017-06-16 21:27 ` Vincent Belaïche
2017-06-16 21:34   ` Philipp Stephani
2017-06-16 21:39     ` Philipp Stephani
2017-06-16 21:52       ` Philipp Stephani
2017-06-16 22:09 ` Vincent Belaïche
2017-06-16 22:23   ` Vincent Belaïche
2017-06-17  5:45     ` Vincent Belaïche
2017-06-17 14:30       ` Philipp Stephani
2017-06-19 10:51         ` Vincent Belaïche
2017-06-26 11:39           ` Philipp Stephani [this message]
2017-06-27  6:05             ` Vincent Belaïche
2017-06-17 14:15     ` Philipp Stephani

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=CAArVCkQmFcwDQ0hzTLuUa1yxNsrYLuGCcHc3MF-be-kMj5p73Q@mail.gmail.com \
    --to=p.stephani2@gmail.com \
    --cc=27391@debbugs.gnu.org \
    --cc=vincent.belaiche@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 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).