unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Jean Louis <bugs@gnu.support>
To: "Nicolas P. Rougier (inria)" <nicolas.rougier@inria.fr>
Cc: emacs-devel@gnu.org
Subject: Re: ELPA: New package: minibuffer-header
Date: Mon, 8 Aug 2022 08:54:34 +0300	[thread overview]
Message-ID: <YvClGpeoYVgqMNzD@protected.localdomain> (raw)
In-Reply-To: <m1wnbkjbc0.fsf@inria.fr>

* Nicolas P. Rougier (inria) <nicolas.rougier@inria.fr> [2022-08-07 18:58]:
> 
> Jean Louis [2022-08-07 at 17:15] wrote:
> > * Nicolas P. Rougier (inria) <nicolas.rougier@inria.fr> [2022-08-07
> > 11:17]:
> > > While I understand your arguments for other minibuffer related >
> > function, I
> > > don't understand how this one makes use of minibuffer.
> > 
> > It is mistake, I was meaning `read-string`:
> 
> Ok. Then with latest version, here is one way to do it:
> 
> #+begin_src emacs-lisp
> (defun help () "Help\n > ")
> 
> (let ((minibuffer-header-format #'help))
>  (read-string ">"))

I did git pull and cannot find that `minibufer-header-format' accepts
option.

And why would option need to be a function?

-- 
Jean

Take action in Free Software Foundation campaigns:
https://www.fsf.org/campaigns

In support of Richard M. Stallman
https://stallmansupport.org/



  reply	other threads:[~2022-08-08  5:54 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-06 15:59 ELPA: New package: minibuffer-header Nicolas P. Rougier (inria)
2022-08-06 16:51 ` Jean Louis
2022-08-06 19:20   ` Nicolas P. Rougier (inria)
2022-08-06 21:21     ` Jean Louis
2022-08-07  8:12       ` Nicolas P. Rougier (inria)
2022-08-07 14:15         ` Jean Louis
2022-08-07 15:55           ` Nicolas P. Rougier (inria)
2022-08-08  5:54             ` Jean Louis [this message]
2022-08-08 21:02               ` Nicolas P. Rougier (inria)
2022-08-06 22:03 ` Stefan Monnier
2022-08-07  8:10   ` Nicolas P. Rougier (inria)

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=YvClGpeoYVgqMNzD@protected.localdomain \
    --to=bugs@gnu.support \
    --cc=emacs-devel@gnu.org \
    --cc=nicolas.rougier@inria.fr \
    /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).