From mboxrd@z Thu Jan 1 00:00:00 1970 X-GM-THRID: 321812168704 X-Google-Groups: supmua X-Google-Thread: 3030fda1bf,57cb6c651ff106d7 X-Google-Attributes: gid3030fda1bf,domainid0,public,googlegroup X-Google-NewGroupId: yes X-Received: by 10.180.105.74 with SMTP id gk10mr2109684wib.0.1414967138584; Sun, 02 Nov 2014 14:25:38 -0800 (PST) X-BeenThere: supmua@googlegroups.com Received: by 10.152.26.228 with SMTP id o4ls357009lag.66.gmail; Sun, 02 Nov 2014 14:25:38 -0800 (PST) X-Received: by 10.112.247.74 with SMTP id yc10mr908024lbc.8.1414967138032; Sun, 02 Nov 2014 14:25:38 -0800 (PST) Return-Path: Received: from mail-lb0-f169.google.com (mail-lb0-f169.google.com. [209.85.217.169]) by gmr-mx.google.com with ESMTPS id ea4si2281621lbc.0.2014.11.02.14.25.37 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sun, 02 Nov 2014 14:25:37 -0800 (PST) Received-SPF: none (google.com: eg@gaute.vetsj.com does not designate permitted sender hosts) client-ip=209.85.217.169; Authentication-Results: gmr-mx.google.com; spf=neutral (google.com: eg@gaute.vetsj.com does not designate permitted sender hosts) smtp.mail=eg@gaute.vetsj.com Received: by mail-lb0-f169.google.com with SMTP id p9so2774515lbv.14 for ; Sun, 02 Nov 2014 14:25:37 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:date:from:subject:to:references:in-reply-to :user-agent:message-id:mime-version:content-type :content-transfer-encoding; bh=mxhxtJT+tn2uW5KkXYDkfDsmMzfTTYwdzNVFIczhN5o=; b=TfLVNL6Qc8bYHJ2m0HVbtFDXEXmyceZWaIZr4y+F5YP/AwlgfaNKSbWxLR3yDpY2lo 7hJR1iPW+0q0ngH9yH+5rTelcO9bQrOBzW72cagkktRyyWZznK5skbLmgS6qDZN2Gh5v XxsMQBK/WigQBGhImIm4wU6JxyOrftUTTs9VZ0RVVl2QD8z9q85VVJkgDR8ycFE3574M qp57qkRqHAzxTPIxsiJG0dgcfbohVhGbl7Hsmmm/1qBVve65+ThW9bnkvMSu/4kqG1I3 7LefjaB9VlphDFt40qpu93K1nvZU2y7JUdgb9luLCM2KIkf1g4lwKf6+qmihQIv3Zlep wvNw== X-Gm-Message-State: ALoCoQkoV48IEj7sqyNQSDWtdtdbDksHvhzS+v1zFFU0ypgl+cSBlUdQo2JbsCwB3aUza2IZHJ1I X-Received: by 10.112.54.162 with SMTP id k2mr46011519lbp.63.1414967137127; Sun, 02 Nov 2014 14:25:37 -0800 (PST) Return-Path: Received: from localhost (cD572BF51.dhcp.as2116.net. [81.191.114.213]) by mx.google.com with ESMTPSA id l11sm7176080lbb.27.2014.11.02.14.25.35 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sun, 02 Nov 2014 14:25:36 -0800 (PST) Date: Sun, 02 Nov 2014 22:25:52 +0000 From: Gaute Hope Subject: Re: [sup] format hook output To: supmua , Ruthard Baudach References: <1414965471-sup-8188@ruthard-lappi> In-Reply-To: <1414965471-sup-8188@ruthard-lappi> User-Agent: astroid/v2612f530 (https://github.com/gauteh/astroid) Message-Id: <1414967097-astroid-0-9hhvxaldxj-26472@strange> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: quoted-printable 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. >=20 > 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. >=20 > 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 =