all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Ihor Radchenko <yantar92@posteo.net>
To: "H. Dieter Wilhelm" <dieter@duenenhof-wilhelm.de>
Cc: emacs-devel@gnu.org
Subject: Re: [ELPA] New package: inform
Date: Tue, 27 Dec 2022 10:54:46 +0000	[thread overview]
Message-ID: <87cz852k21.fsf@localhost> (raw)
In-Reply-To: <867cydrj7e.fsf@duenenhof-wilhelm.de>

"H. Dieter Wilhelm" <dieter@duenenhof-wilhelm.de> writes:

>> I think the last code I saw was sill a prototype, but I can't remember
>> reviewing it, really :-(
>
> I think I suggested putting it on Melpa to see if there's a real
> interest in it (up to now there were 432 downloads, please see
> https://melpa.org/#/?q=inform).  My idea of getting some feedback, hints
> or even bug reports were in vain, though.

There is real interest to make it part of info.el :)
Right from Emacs devs.

" I think it would make sense to integrate it directly into `info.el`."
                 Stefan Monnier <monnier@iro.umontreal.ca> (2020-05-07)

You don't need to publish this as separate package to fix bugs. You will
not fix all of them anyway, and you have more chances to get bug reports
for a core code.

>> It would be good to get a bug-nb for it and send the latest version of
>> he suggested patch to it.
>
> Sorry, what do you mean by bug-nb?

Bug number. Basically: "send it via M-x report-emacs-bug attaching a
patch against Emacs master branch".

Then, we can discuss the implementation and not loose it in emacs-devel
archives. A "bug" will be tracked.

-- 
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at <https://orgmode.org/>.
Support Org development at <https://liberapay.com/org-mode>,
or support my work at <https://liberapay.com/yantar92>



  reply	other threads:[~2022-12-27 10:54 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-07 19:36 [ELPA] New package: inform H. Dieter Wilhelm
2020-05-07 20:40 ` Stefan Monnier
2020-05-08  1:34   ` T.V Raman
2020-05-08  8:29     ` H. Dieter Wilhelm
2020-05-08  8:18   ` H. Dieter Wilhelm
2020-05-08 10:25     ` Eli Zaretskii
2020-05-08 11:06       ` H. Dieter Wilhelm
2020-05-08 11:39         ` Eli Zaretskii
2020-05-08 13:45         ` H. Dieter Wilhelm
2020-05-08 14:01           ` Eli Zaretskii
2020-05-08 15:04           ` Stefan Monnier
2020-05-10 18:19             ` H. Dieter Wilhelm
2022-12-25  9:39               ` Ihor Radchenko
2022-12-26  0:10                 ` Stefan Monnier
2022-12-26 20:41                   ` H. Dieter Wilhelm
2022-12-27 10:54                     ` Ihor Radchenko [this message]
2022-12-27 22:38                       ` H. Dieter Wilhelm
2020-05-08 11:45       ` Maurizio Boriani
2020-05-08 16:23     ` Drew Adams
2020-05-08 16:38       ` Drew Adams
2020-05-08 18:53       ` H. Dieter Wilhelm
2020-05-08 21:55         ` Drew Adams
2020-05-08 22:02           ` Drew Adams
2020-05-09  9:46       ` Jean-Christophe Helary
2020-05-09 13:06         ` help-fns+ (WAS: [ELPA] New package: inform) Noam Postavsky
2020-05-09 13:16           ` Jean-Christophe Helary
2020-05-09 17:27         ` [ELPA] New package: inform Drew Adams
2020-05-10  1:05           ` Jean-Christophe Helary
2020-05-09 17:10   ` H. Dieter Wilhelm
2023-02-01 19:08   ` H. Dieter Wilhelm
2023-02-01 19:21     ` H. Dieter Wilhelm
2020-05-09  3:51 ` Richard Stallman
2020-05-09  9:38   ` H. Dieter Wilhelm
2020-05-09  9:51     ` Eli Zaretskii
2020-05-09 15:29       ` H. Dieter Wilhelm

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=87cz852k21.fsf@localhost \
    --to=yantar92@posteo.net \
    --cc=dieter@duenenhof-wilhelm.de \
    --cc=emacs-devel@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 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.