emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Arash Esbati <arash@gnu.org>
To: emacs-orgmode@gnu.org
Subject: [PATCH] Fix one remaining emacs-30 byte-compile warning
Date: Tue, 24 Jan 2023 10:29:17 +0100	[thread overview]
Message-ID: <86h6wgmgb6.fsf@gnu.org> (raw)

Hi all,

Robert sent a patch[1] which pacifies emacs-30 compiler warning.  He
missed one which is fixed by the patch below.  It is against org-mode
master (6b15897a56).

Footnotes:
[1]  https://lists.gnu.org/archive/html/emacs-orgmode/2023-01/msg00743.html

Best, Arash

--8<---------------cut here---------------start------------->8---
diff --git a/lisp/ox.el b/lisp/ox.el
index ebf89bb..4c84686 100644
--- a/lisp/ox.el
+++ b/lisp/ox.el
@@ -6683,14 +6683,14 @@ see.
 Optional argument POST-PROCESS is a function which should accept
 no argument.  It is always called within the current process,
 from BUFFER, with point at its beginning.  Export back-ends can
-use it to set a major mode there, e.g,
+use it to set a major mode there, e.g.,

   (defun org-latex-export-as-latex
     (&optional async subtreep visible-only body-only ext-plist)
     (interactive)
     (org-export-to-buffer \\='latex \"*Org LATEX Export*\"
       async subtreep visible-only body-only ext-plist
-      #'LaTeX-mode))
+      #\\='LaTeX-mode))

 When expressed as an anonymous function, using `lambda',
 POST-PROCESS needs to be quoted.
--8<---------------cut here---------------end--------------->8---


             reply	other threads:[~2023-01-25  4:51 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-24  9:29 Arash Esbati [this message]
2023-01-25 11:58 ` [PATCH] Fix one remaining emacs-30 byte-compile warning Ihor Radchenko
2023-01-25 15:45   ` Arash Esbati
2023-01-26  9:22     ` Ihor Radchenko
2023-01-26 10:43       ` Arash Esbati
2023-01-27 13:01         ` Ihor Radchenko
2023-03-22 14:00           ` Bastien Guerry
2023-03-22 14:38             ` Ihor Radchenko
2023-01-25 13:48 ` Robert Pluim
2023-01-25 15:53   ` Arash Esbati

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.orgmode.org/

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

  git send-email \
    --in-reply-to=86h6wgmgb6.fsf@gnu.org \
    --to=arash@gnu.org \
    --cc=emacs-orgmode@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/org-mode.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).