unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Philipp Stephani <p.stephani2@gmail.com>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 23486@debbugs.gnu.org, Noam Postavsky <npostavs@users.sourceforge.net>
Subject: bug#23486: 25.0.93; Modules: features missing from make_function
Date: Sun, 13 Sep 2020 11:44:18 +0200	[thread overview]
Message-ID: <CAArVCkQvj_oQypK9hVJWmhx7-vT5bmHXgFDMCf+ZUKedz3bGJg@mail.gmail.com> (raw)
In-Reply-To: <87pn70495j.fsf@gnus.org>

Am Sa., 5. Sept. 2020 um 15:59 Uhr schrieb Lars Ingebrigtsen <larsi@gnus.org>:
>
> npostavs@users.sourceforge.net writes:
>
> > Philipp Stephani <p.stephani2@gmail.com> writes:
> >
> >> This is now done (commit
> >> 31fded0370c3aa6d2c4370cae21cdb7475873483). This fixes (1) through
> >> (3). (4) through (6) are still open. That's probably OK if the
> >> limitations are documented; modules can always do the equivalent of
> >> (eval ' (defun ...)) to get complete support.
> >
> > Lisp_Subr's have an intspec field (4), but I agree it's not really
> > essential.  As I think you mentioned in the OP, supporting `declare' (5)
> > is not doable by definition (because the effects of 'declare' operate on
> > the symbol, not the function object).
> >
> > Docstrings containing null or non-Unicode characters (6) just seems
> > completely pointless to me.  Are there any cases using that capability
> > in Emacs (or outside Emacs)?  I would probably consider them as bugs.
>
> This was the final message in this thread.  Philipp's patch fixed the
> main problems, and (5) and (6) doesn't sound like something that
> can/should be fixed.  Which leaves (4), which didn't seem essential,
> either.
>
> So is there more to be done here, or should this bug report be closed?
>

I'd still like to fix (4), just for completeness's sake. How about
introducing {get,set}_interactive_spec, just like
{get,set}_function_finalizer?





  reply	other threads:[~2020-09-13  9:44 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-09 16:37 bug#23486: 25.0.93; Modules: features missing from make_function Philipp Stephani
2016-09-11 14:13 ` Philipp Stephani
2016-09-11 14:57 ` npostavs
2017-03-26 20:02   ` Philipp Stephani
2017-03-26 20:22     ` npostavs
2017-03-26 20:40       ` Philipp Stephani
2017-03-27  3:57 ` npostavs
2017-07-04 18:20   ` Philipp Stephani
2017-07-05  3:40     ` npostavs
2020-09-05 13:59       ` Lars Ingebrigtsen
2020-09-13  9:44         ` Philipp Stephani [this message]
2020-09-13 13:20           ` Lars Ingebrigtsen
2020-09-13 18:50             ` Philipp Stephani
2020-12-07 16:42               ` Lars Ingebrigtsen
2020-12-12 14:31                 ` 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=CAArVCkQvj_oQypK9hVJWmhx7-vT5bmHXgFDMCf+ZUKedz3bGJg@mail.gmail.com \
    --to=p.stephani2@gmail.com \
    --cc=23486@debbugs.gnu.org \
    --cc=larsi@gnus.org \
    --cc=npostavs@users.sourceforge.net \
    /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).