all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Michael Albinus <michael.albinus@gmx.de>
To: "João Távora" <joaotavora@gmail.com>
Cc: Stefan Monnier <monnier@iro.umontreal.ca>,
	emacs-devel <emacs-devel@gnu.org>
Subject: Re: master 43fded1: Add lisp-data-mode for editing non-code Lisp data
Date: Sat, 02 May 2020 13:20:03 +0200	[thread overview]
Message-ID: <87k11uy464.fsf@gmx.de> (raw)
In-Reply-To: <CALDnm52NF=Qx6+=hhMgnpnvffNOVdS7G=15jRm=Fiprdva-OnQ@mail.gmail.com> ("João Távora"'s message of "Sat, 2 May 2020 11:45:33 +0100")

João Távora <joaotavora@gmail.com> writes:

Hi João,

> I think what Stefan is saying is that the probability that you are going
> to use Emacs <28 to visit a file produced by Emacs 28 is low.  And the
> adverse effects are an error message that I personally could live with
> on those (presumably rare) occasions.

At least I do it daily :-)

And the problem is not the error message. The emacs-lisp cookie is there
for a reason; I want to get syntax highlighting in that file.

> João

Best regards, Michael.



  reply	other threads:[~2020-05-02 11:20 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20200501111127.16683.2701@vcs0.savannah.gnu.org>
     [not found] ` <20200501111128.D311220B5B@vcs0.savannah.gnu.org>
2020-05-01 17:52   ` master 43fded1: Add lisp-data-mode for editing non-code Lisp data Michael Albinus
2020-05-01 18:18     ` Stefan Monnier
2020-05-02 10:32       ` Michael Albinus
2020-05-02 10:45         ` João Távora
2020-05-02 11:20           ` Michael Albinus [this message]
2020-05-02 11:22             ` João Távora
2020-05-02 14:08         ` Stefan Monnier
2020-05-02 14:16           ` Michael Albinus
2020-05-01 18:40     ` João Távora
2020-05-02 10:51       ` Michael Albinus

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=87k11uy464.fsf@gmx.de \
    --to=michael.albinus@gmx.de \
    --cc=emacs-devel@gnu.org \
    --cc=joaotavora@gmail.com \
    --cc=monnier@iro.umontreal.ca \
    /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.