From: TS <debts@xk2c.de>
To: Bart Schaefer <schaefer@brasslantern.com>,
Zsh hackers list <zsh-workers@zsh.org>
Subject: Re: Zsh: [7] + 23074 suspended (tty output)
Date: Sun, 16 Sep 2018 17:40:48 +0200 [thread overview]
Message-ID: <9b969afc-6241-b7ab-32cc-cd3b37d6cb9c@xk2c.de> (raw)
In-Reply-To: <20180916084020.GA19815@zira.vinc17.org>
[-- Attachment #1: Type: text/plain, Size: 1137 bytes --]
Hello
Vincent Lefevre schrieb/wrote:
> On 2018-09-15 21:06:56 +0200, TS wrote:
>> Test case, tested with 5.6.2:
>> https://bugs.debian.org/cgi-bin/bugreport.cgi?att=1;bug=908818;filename=.zshrc;msg=66
>>
>> result for me:
>> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=908818#66
>
> I think I have noticed issues with "less" using zsh-5.6.1-10-g24bb465
> but I didn't remember what I did exactly and I couldn't reproduce
> them. I needed to do a fg.
I have now tried different iterations of that minimal .zshrc.
It seems only when less is wrapped inside a function i get this
"zsh: suspended (tty output)".
But when less is wrapped inside a function like this, it is rather reliable
replicable.
steps to show the issue:
1) ~/.zshrc as attached
2) exec zsh or login
e.g.:
% exec zsh
zsh: suspended (tty output)
i have a testuser for such things, therefore i "su -l" to him first.
But according to my tests, the "su -l" part is irrelevant for the issue.
Only the "less wrapped in function" part seem to matter.
I earlier versions of Zsh that did not make a difference.
Thanks for taking a look.
kind regards,
Thilo
[-- Attachment #2: .zshrc --]
[-- Type: text/plain, Size: 66 bytes --]
builtin zmodload zsh/zprof
lessx() {
=less
}
zprof |& lessx
next prev parent reply other threads:[~2018-09-16 15:41 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-15 17:22 TS
2018-09-15 18:10 ` Bart Schaefer
2018-09-15 18:51 ` TS
2018-09-15 19:06 ` TS
2018-09-16 8:40 ` Vincent Lefevre
2018-09-16 15:40 ` TS [this message]
2018-09-16 17:51 ` Peter Stephenson
2018-09-17 20:13 ` TS
2018-09-18 17:59 ` Peter Stephenson
2018-09-18 1:16 ` Vincent Lefevre
2018-09-18 17:58 ` Peter Stephenson
2018-09-20 12:01 ` Vincent Lefevre
2018-09-20 16:11 ` Daniel Shahaf
2018-09-18 19:30 ` TS
2018-09-19 3:38 ` TS
2018-09-19 14:23 ` Daniel Tameling
2018-09-19 16:12 ` Peter Stephenson
2018-09-19 18:15 ` TS
2018-09-17 14:01 ` Sebastian Gniazdowski
2018-09-17 14:49 ` Valgrind tests (was: Re: Zsh: [7] + 23074 suspended (tty output)) Daniel Shahaf
2018-09-18 5:21 ` Sebastian Gniazdowski
2018-09-18 15:55 ` Daniel Shahaf
2018-09-19 5:04 ` Sebastian Gniazdowski
2019-07-03 23:29 ` Sebastian Gniazdowski
2019-07-03 23:31 ` Sebastian Gniazdowski
2019-07-03 23:45 ` Sebastian Gniazdowski
2019-07-13 14:31 ` Sebastian Gniazdowski
2019-07-14 6:39 ` Daniel Shahaf
2019-07-14 22:17 ` Sebastian Gniazdowski
2019-07-15 8:54 ` Peter Stephenson
2019-07-15 9:29 ` Peter Stephenson
2019-07-15 18:45 ` Sebastian Gniazdowski
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=9b969afc-6241-b7ab-32cc-cd3b37d6cb9c@xk2c.de \
--to=debts@xk2c.de \
--cc=schaefer@brasslantern.com \
--cc=zsh-workers@zsh.org \
/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.vuxu.org/mirror/zsh/
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 NNTP newsgroup(s).