unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: martin rudalics <rudalics@gmx.at>
To: Geralt <usr.gentoo@googlemail.com>
Cc: emacs-devel@gnu.org
Subject: Re: ElDoc: adding optional support to display messages in header-line instead of the echo area
Date: Tue, 04 Aug 2009 10:32:19 +0200	[thread overview]
Message-ID: <4A77F213.6070808@gmx.at> (raw)
In-Reply-To: <fbdd0e50908031447m72fd8a8bo16e71ca77e2721e4@mail.gmail.com>

 > can you explain why? I put the omessage into the ELSE block because
 > somebody on emacs-help suggested it and it made sense to me at that
 > time.

Compiling eldoc.el after applying your patch gets me

eldoc-new.el~:550:1:Warning: the function `omessage' is not known to be
     defined.

This happens because in the

       (cond (eldoc-last-message (if eldoc-display-in-header-line
				    (setq header-line-format eldoc-last-message)
				  (message "%s" eldoc-last-message)
				  (omessage (message nil)))))))

form you misplaced the parentheses and thus `omessage' is not considered
a condition of some clause of the `cond' special form but as a function
call.

BTW, I suppose you also need to call `force-mode-line-update' because
Emacs does not necessarily update the contents of the header line when
just moving point.

martin




  parent reply	other threads:[~2009-08-04  8:32 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-01  9:46 ElDoc: adding optional support to display messages in header-line instead of the echo area Geralt
2009-08-02  9:33 ` martin rudalics
2009-08-03 21:47   ` Geralt
2009-08-04  7:10     ` Tassilo Horn
2009-08-04  8:32     ` martin rudalics [this message]
2009-08-04 18:50       ` Geralt
2009-08-04 17:05 ` ElDoc: adding optional support to display messages in header-line Stefan Monnier
2009-08-04 19:05   ` Geralt
2009-08-05  2:00     ` Stefan Monnier
2009-08-06 18:50       ` Geralt
2009-08-04 17:07 ` Stefan Monnier
2009-08-04 19:06   ` Geralt

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=4A77F213.6070808@gmx.at \
    --to=rudalics@gmx.at \
    --cc=emacs-devel@gnu.org \
    --cc=usr.gentoo@googlemail.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).