Discussions of development and use of the Sup email client
 help / color / mirror / Atom feed
From: Gaute Hope <eg@gaute.vetsj.com>
To: supmua <supmua@googlegroups.com>,
	Ruthard Baudach <ruthard.baudach@web.de>
Subject: Re: [sup] format hook output
Date: Sun, 02 Nov 2014 22:25:52 +0000	[thread overview]
Message-ID: <1414967097-astroid-0-9hhvxaldxj-26472@strange> (raw)
In-Reply-To: <1414965471-sup-8188@ruthard-lappi>

Excerpts from Ruthard Baudach's message of November 2, 2014 23:03:
> If I puts or print something inside a hook, it is put on the bottom of
> sup.
> 
> One problem is, that \n does only produce a "next line" and no "carraige
> return", a problem often occoring if you try to print to a curses
> controlled terminal.
> 
> How do I output some information in a curses-compliant way from a hook?
> Or where would be a good starting point to search the code of sup?

Hi,

You can use the buffermanager `say` methods or the log methods. When in
ncurses mode regular puts to stdout will only mess up stuff.

Cheers, Gaute



      reply	other threads:[~2014-11-02 22:25 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-02 22:03 Ruthard Baudach
2014-11-02 22:25 ` Gaute Hope [this message]

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=1414967097-astroid-0-9hhvxaldxj-26472@strange \
    --to=eg@gaute.vetsj.com \
    --cc=ruthard.baudach@web.de \
    --cc=supmua@googlegroups.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox