More noticeable version of (message)

More noticeable version of (message)

[Craig Muth]

[-- Attachment #1: Type: text/plain, Size: 238 bytes --]

I often don't notice the output of lines like (message "hi"), especially
when in full-screen mode.

Any ideas?  Not a huge fan of beeping because I associate that with an
error.  I'm on a mac so any face/font stuff is fair game.

--Craig

[-- Attachment #2: Type: text/html, Size: 333 bytes --]

Re: More noticeable version of (message)

[Peter Münster]

On Tue, Nov 01 2011, Craig Muth wrote:

> Any ideas?  Not a huge fan of beeping because I associate that with
> an error.  I'm on a mac so any face/font stuff is fair game.

There is:
(require 'notifications)
(notifications-notify ...)

(I don't know, if this works on a mac...)

-- 
           Peter

Re: More noticeable version of (message)

[Jambunathan K]

Craig Muth <craig.muth@gmail.com> writes:

> I often don't notice the output of lines like (message "hi"),
> especially when in full-screen mode.
>
> Any ideas?  Not a huge fan of beeping because I associate that with
> an error.  I'm on a mac so any face/font stuff is fair game.

Try this:

(fset 'message-plain (symbol-function 'message))

(defun message-colored (fmt-string &rest args)
  (message-plain 
   (propertize
    (apply 'format fmt-string args)
    'face 'font-lock-comment-face)))

(fset 'message 'message-colored)

You will see that the messages appear in comment face.

> --Craig
>
>
>

-- 

Re: More noticeable version of (message)

[Jambunathan K]

Jambunathan K <kjambunathan@gmail.com> writes:

> Craig Muth <craig.muth@gmail.com> writes:
>
>> I often don't notice the output of lines like (message "hi"),
>> especially when in full-screen mode.
>>
>> Any ideas?  Not a huge fan of beeping because I associate that with
>> an error.  I'm on a mac so any face/font stuff is fair game.
>
> Try this:
>
> (fset 'message-plain (symbol-function 'message))
>
> (defun message-colored (fmt-string &rest args)
>   (message-plain 
>    (propertize
>     (apply 'format fmt-string args)
>     'face 'font-lock-comment-face)))
>
> (fset 'message 'message-colored)
> You will see that the messages appear in comment face.

This is an elegant variation of the above.

(defadvice message 
  (before colored-message activate)
  (ad-set-arg 0 (propertize (ad-get-arg 0) 'face 'font-lock-comment-face)))

>> --Craig
>>
>>
>>

-- 

Re: More noticeable version of (message)

[Yagnesh Raghava Yakkala]

Hi Jambunathan,

Jambunathan K <kjambunathan@gmail.com> writes:

> Jambunathan K <kjambunathan@gmail.com> writes:
>
>> Craig Muth <craig.muth@gmail.com> writes:
>>
>>> I often don't notice the output of lines like (message "hi"),
>>> especially when in full-screen mode.
>>>
>>> Any ideas?  Not a huge fan of beeping because I associate that with
>>> an error.  I'm on a mac so any face/font stuff is fair game.
>>
>> Try this:
>>
>> (fset 'message-plain (symbol-function 'message))
>>
>> (defun message-colored (fmt-string &rest args)
>>   (message-plain 
>>    (propertize
>>     (apply 'format fmt-string args)
>>     'face 'font-lock-comment-face)))
>>
>> (fset 'message 'message-colored)
>> You will see that the messages appear in comment face.
>
> This is an elegant variation of the above.

>
> (defadvice message 
>   (before colored-message activate)
>   (ad-set-arg 0 (propertize (ad-get-arg 0) 'face 'font-lock-comment-face)))
>

Noob here.

If I may I ask, is the above defadvise supposed show the
messages in font-lock-comment-face.?

after evaluating the above, a test gets me the following.
------------------
(message "test")
  =>
  #("test" 0 4 (face font-lock-comment-face))
------------------


>>> --Craig
>>>
>>>
>>>

-- 
YYR

Re: More noticeable version of (message)

[Jambunathan K]

Yagnesh Raghava Yakkala <yagnesh@live.com> writes:

> Hi Jambunathan,
>
> Jambunathan K <kjambunathan@gmail.com> writes:
>
>> Jambunathan K <kjambunathan@gmail.com> writes:
>>
>>> Craig Muth <craig.muth@gmail.com> writes:
>>>
>>>> I often don't notice the output of lines like (message "hi"),
>>>> especially when in full-screen mode.
>>>>
>>>> Any ideas?  Not a huge fan of beeping because I associate that with
>>>> an error.  I'm on a mac so any face/font stuff is fair game.
>>>
>>> Try this:
>>>
>>> (fset 'message-plain (symbol-function 'message))
>>>
>>> (defun message-colored (fmt-string &rest args)
>>>   (message-plain 
>>>    (propertize
>>>     (apply 'format fmt-string args)
>>>     'face 'font-lock-comment-face)))
>>>
>>> (fset 'message 'message-colored)
>>> You will see that the messages appear in comment face.
>>
>> This is an elegant variation of the above.
>
>>
>> (defadvice message 
>>   (before colored-message activate)
>>   (ad-set-arg 0 (propertize (ad-get-arg 0) 'face 'font-lock-comment-face)))
>>
>
> Noob here.
>
> If I may I ask, is the above defadvise supposed show the
> messages in font-lock-comment-face.?
>
> after evaluating the above, a test gets me the following.
> ------------------
> (message "test")
>   =>
>   #("test" 0 4 (face font-lock-comment-face))
> ------------------

When you eval by hand (using M-: or C-x C-e) the echoed message which is
fontified gets immediately replaced with the return val from message. So
the value that you see above is a stringified version of propertized
text.

Try the below snippet:

(defun hello-world () 
  (interactive)
  (message "hello world"))

M-x hello-world RET

>
>>>> --Craig
>>>>
>>>>
>>>>

-- 

Re: More noticeable version of (message)

[Lennart Borgman]

On Thu, Nov 3, 2011 at 17:23, Jambunathan K <kjambunathan@gmail.com> wrote:
> Yagnesh Raghava Yakkala <yagnesh@live.com> writes:
>
>> Hi Jambunathan,
>>
>> Jambunathan K <kjambunathan@gmail.com> writes:
>>
>>> Jambunathan K <kjambunathan@gmail.com> writes:
>>>
>>>> Craig Muth <craig.muth@gmail.com> writes:
>>>>
>>>>> I often don't notice the output of lines like (message "hi"),
>>>>> especially when in full-screen mode.
>>>>>
>>>>> Any ideas?  Not a huge fan of beeping because I associate that with
>>>>> an error.  I'm on a mac so any face/font stuff is fair game.
>>>>
>>>> Try this:
>>>>
>>>> (fset 'message-plain (symbol-function 'message))
>>>>
>>>> (defun message-colored (fmt-string &rest args)
>>>>   (message-plain
>>>>    (propertize
>>>>     (apply 'format fmt-string args)
>>>>     'face 'font-lock-comment-face)))
>>>>
>>>> (fset 'message 'message-colored)
>>>> You will see that the messages appear in comment face.
>>>
>>> This is an elegant variation of the above.
>>
>>>
>>> (defadvice message
>>>   (before colored-message activate)
>>>   (ad-set-arg 0 (propertize (ad-get-arg 0) 'face 'font-lock-comment-face)))

Here is the version I am using in nXhtml:


(defun web-vcs-message-with-face (face format-string &rest args)
  "Display a colored message at the bottom of the string.
FACE is the face to use for the message.
FORMAT-STRING and ARGS are the same as for `message'.

Also put FACE on the message in *Messages* buffer."
  (with-current-buffer "*Messages*"
    (save-restriction
      (widen)
      (let* ((start (let ((here (point)))
                      (goto-char (point-max))
                      (prog1
                          (copy-marker
                           (if (bolp) (point-max)
                             (1+ (point-max))))
                        (goto-char here))))
             (msg-with-face (propertize (apply 'format format-string args)
                                        'face face)))
        ;; This is for the echo area:
        (message "%s" msg-with-face)
        ;; This is for the buffer:
        (when (< 0 (length msg-with-face))
          (goto-char (1- (point-max)))
          ;;(backward-char)
          ;;(unless (eolp) (goto-char (line-end-position)))
          (put-text-property start (point)
                             'face face))))))

Re: More noticeable version of (message)

[chad]

This looks like it's designed to markup the *Messages* buffer only; is
that correct? I was going to suggest to the OP that, especially when
in fullscreen mode, he consider arranging to have a (emacs) window
showing *Messages* by default, but decided that it was a case of
telling the user to change to match the program. If you have already
automated the process of ``keep a few lines of *Messages* visible all
the time'', that might be useful beyond nXhtml users.  

Thanks,
*Chad

On Nov 3, 2011, at 11:16 AM, Lennart Borgman wrote:
> 
> Here is the version I am using in nXhtml: […]

Re: More noticeable version of (message)

[Lennart Borgman]

No it should color both the echo area and the *Messages* buffer. Try this:

(defun hello-temp ()
  (interactive)
  (web-vcs-message-with-face
   'font-lock-warning-face
   "hello!"
   ))

On Thu, Nov 3, 2011 at 23:44, chad <yandros@mit.edu> wrote:
> This looks like it's designed to markup the *Messages* buffer only; is
> that correct? I was going to suggest to the OP that, especially when
> in fullscreen mode, he consider arranging to have a (emacs) window
> showing *Messages* by default, but decided that it was a case of
> telling the user to change to match the program. If you have already
> automated the process of ``keep a few lines of *Messages* visible all
> the time'', that might be useful beyond nXhtml users.
>
> Thanks,
> *Chad
>
> On Nov 3, 2011, at 11:16 AM, Lennart Borgman wrote:
>>
>> Here is the version I am using in nXhtml: […]
>
>

Re: More noticeable version of (message)

[Juri Linkov]

> No it should color both the echo area and the *Messages* buffer. Try this:

Shouldn't the *Message* buffer keep properties of inserted text?

Re: More noticeable version of (message)

[Juri Linkov]

>> No it should color both the echo area and the *Messages* buffer. Try this:
>
> Shouldn't the *Message* buffer keep properties of inserted text?

BTW, there is a strange effect in the *Message* buffer:

1. split window: `C-x 2'
2. visit Dired in one window: `C-x d RET'
3. open the *Messages* buffer in another window: `C-x o C-h e C-x o'
4. type `w' a few times on different files in Dired.  It echoes filenames
   in the echo area, but the *Messages* buffer is not updated.
5. select another window with the *Messages* buffer: `C-x o'.
   All previous messages suddenly are flushed to it.

Re: More noticeable version of (message)

[Lennart Borgman]

On Sun, Nov 6, 2011 at 15:57, Juri Linkov <juri@jurta.org> wrote:
>>> No it should color both the echo area and the *Messages* buffer. Try this:
>>
>> Shouldn't the *Message* buffer keep properties of inserted text?
>
> BTW, there is a strange effect in the *Message* buffer:
>
> 1. split window: `C-x 2'
> 2. visit Dired in one window: `C-x d RET'
> 3. open the *Messages* buffer in another window: `C-x o C-h e C-x o'
> 4. type `w' a few times on different files in Dired.  It echoes filenames
>   in the echo area, but the *Messages* buffer is not updated.
> 5. select another window with the *Messages* buffer: `C-x o'.
>   All previous messages suddenly are flushed to it.

Yes, the window displaying *Messages* should be updated immediately.
There is in performance problem with that.