From: Michael Heerdegen <michael_heerdegen@web.de>
To: help-gnu-emacs@gnu.org
Cc: Stefan Monnier <monnier@iro.umontreal.ca>
Subject: Re: custom record separator in forms-mode?
Date: Sat, 26 Dec 2020 16:09:06 +0100 [thread overview]
Message-ID: <875z4o38q5.fsf@web.de> (raw)
In-Reply-To: 87bleg3bte.fsf@web.de
Hello,
this probably changed the behavior (and probably inadvertently):
84e0b7dad6f1a8e53261f9b96f5a9080fea681a4
Author: Stefan Monnier <monnier@iro.umontreal.ca>
Deprecate `intangible' and `point-entered' properties
modified lisp/forms.el
@@ -650,1 +650,1 @@
- (run-hooks 'read-file-filter)
+ (mapc #'funcall read-file-filter)
> > Debugger entered--Lisp error: (wrong-type-argument sequencep
> > filter-read-205-newline)
> > mapc(funcall filter-read-205-newline)
> > forms-mode()
> > funcall-interactively(forms-mode)
> > call-interactively(forms-mode record nil)
> > command-execute(forms-mode record)
> > execute-extended-command(nil "forms-mode" "for")
> > funcall-interactively(execute-extended-command nil "forms-mode" "for")
> > call-interactively(execute-extended-command nil nil)
> > command-execute(execute-extended-command)
>
> Thanks. Hmm, it seems `forms-read-file-filter' is expected to be a list
> of functions (a hook), in contradiction to what the docstring says
> (documentation bug). It also seems that OTOH `forms-write-file-filter'
> is expected to be a function.
Michael.
next prev parent reply other threads:[~2020-12-26 15:09 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-24 16:57 custom record separator in forms-mode? Timo Myyrä
2020-12-26 7:34 ` Michael Heerdegen
2020-12-26 11:33 ` Timo Myyrä
2020-12-26 14:02 ` Michael Heerdegen
2020-12-26 15:09 ` Michael Heerdegen [this message]
2020-12-26 17:22 ` Stefan Monnier
2020-12-27 6:01 ` Michael Heerdegen
2020-12-27 6:31 ` Michael Heerdegen
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=875z4o38q5.fsf@web.de \
--to=michael_heerdegen@web.de \
--cc=help-gnu-emacs@gnu.org \
--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.
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).