From: Jim <firstname.lastname@example.org> To: zsh <email@example.com> Subject: I can't explain the following Date: Tue, 26 Apr 2022 10:49:50 -0500 [thread overview] Message-ID: <CA+rB6GK-z6DD-nNwLtUZqwUfo+T=oV3+iQDPEpnVCzsVtT1K2A@mail.gmail.com> (raw) [-- Attachment #1: Type: text/plain, Size: 1066 bytes --] Hi everyone, While working on my .zshenv file I discovered something strange that I can't explain. The changes(still a work in progress) had a glob that took some time to complete and won't be there when I finish. This made it quite noticeable. Everything I was doing in a zsh instance seemed to work normally with one notable exception, that I know of. % less $file # executes .zshenv before outputting content of file If .zshrc has some "test" print statement(s), they are outputs and not the file?? % < $file outputs file and pipes it through less ? I should remember why, anyway! % cat $file outputs content of file as expected % more $file outputs content of file as expected What I can't figure out is why zsh/"less" does what it does. Could someone enlighten me? Is there a way of "tracing" what is happening? BTW "less" is not an alias or function. Distribution: Devuan ZSH_VERSION 5.8 ZSH_PATCHLEVEL debian/5.8-6+deb11u1 LESS='-R -M --shift 5' LESSOPEN='|lesspipe %s' Thanks in advance for any help you can provide. Jim Murphy [-- Attachment #2: Type: text/html, Size: 1510 bytes --]
next reply other threads:[~2022-04-26 15:52 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-04-26 15:49 Jim [this message] 2022-04-27 1:22 ` Bart Schaefer 2022-04-27 15:20 ` Jim 2022-04-27 15:59 ` Bart Schaefer 2022-04-27 17:47 ` Jim
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='CA+rB6GK-z6DD-nNwLtUZqwUfo+T=oV3+iQDPEpnVCzsVtT1K2A@mail.gmail.com' \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --subject='Re: I can'\''t explain the following' \ /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
Code repositories for project(s) associated with this 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).