unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Andrea Corallo <acorallo@gnu.org>
To: "Mattias Engdegård" <mattias.engdegard@gmail.com>
Cc: Andrea Corallo <akrl@sdf.org>,  Eli Zaretskii <eliz@gnu.org>,
	emacs-devel <emacs-devel@gnu.org>
Subject: Re: Inferred function types in the *Help* buffer
Date: Tue, 30 May 2023 14:48:52 -0400	[thread overview]
Message-ID: <yp1jzwpodt7.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <E894A20E-4740-422A-9006-701DE935196B@gmail.com> ("Mattias Engdegård"'s message of "Tue, 30 May 2023 20:14:21 +0200")

Mattias Engdegård <mattias.engdegard@gmail.com> writes:

> 30 maj 2023 kl. 18.46 skrev Andrea Corallo <acorallo@gnu.org>:
>
>> Ideally I think we should have a declare syntax and maybe an extention
>> to the DEFUN macro to cover for primitives as well, in order to have
>> these declaration where each function is defined.
>
> That would probably be a good thing in the long run, yes. There are other declarations we would like to be able to attach to DEFUN as well.

Hi Mattias,

thanks for your feedback.

yep agree, I think we should convey on a syntax for everything we want
to express (type and other properties), so we have something to
implement on the long run both for the Lisp both for the C side.

>>  But probably for now
>> something like the attached patch is sufficient and considerably less
>> invasive?
>
> Actually it sort of increases coupling; I'd rather it stayed in
> comp.el for the time being. You could write a function (in comp.el)
> for access.

The main reason why I'd like to move them out is not to require the load
of comp.el for a simple C-h f.  Secondary yeah I think that if it's in
use outside the compilation functionality should just not live there.

Anyway I'm happy with any solution (as long as we find one :).

Thanks

  Andrea



  reply	other threads:[~2023-05-30 18:48 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-23 16:44 Inferred function types in the *Help* buffer Andrea Corallo
2023-05-24 10:46 ` Eli Zaretskii
2023-05-24 12:19   ` Andrea Corallo
2023-05-30 16:46     ` Andrea Corallo
2023-05-30 18:14       ` Mattias Engdegård
2023-05-30 18:48         ` Andrea Corallo [this message]
2023-05-31 12:19           ` Andrea Corallo
2023-05-31 14:08             ` Eli Zaretskii
2023-06-01 11:28             ` Mattias Engdegård
2023-06-01 11:35               ` Eli Zaretskii
2023-06-01 11:36                 ` Mattias Engdegård
2023-06-01 11:54                   ` Andrea Corallo
2023-06-01 11:50               ` Andrea Corallo
2023-06-01 13:06                 ` Mattias Engdegård
2023-06-01 13:34                   ` Andrea Corallo
2023-06-01 14:50                     ` Mattias Engdegård
2023-06-01 15:10                       ` Andrea Corallo
2023-06-01 17:53                         ` Mattias Engdegård
2023-06-01 19:13                           ` Andrea Corallo
2023-06-01 14:09                   ` Andrea Corallo
2023-05-31 13:46       ` Eli Zaretskii
2023-06-01  8:42         ` Andrea Corallo
2023-06-01  8:53           ` Eli Zaretskii
  -- strict thread matches above, loose matches on Subject: below --
2023-05-23 16:47 Payas Relekar
2023-05-23 18:51 ` Philip Kaludercic
2023-05-24 12:20 ` Andrea Corallo

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=yp1jzwpodt7.fsf@fencepost.gnu.org \
    --to=acorallo@gnu.org \
    --cc=akrl@sdf.org \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=mattias.engdegard@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).