Ed Maste writes:
> It looks like nano's post-install/-deinstall requires print/indexinfo
> and it's not available. This doesn't appear to be directly related to
> /bin/sh, /bin/tcsh, or pkgbase. If you have concise reproduction
> steps, please submit a PR.
The
erience (good) with the
> 15.0-CURRENT experience.
>
> It seems that /bin/tcsh no longer works around the issue that affects
> the print/indexinfo package with /bin/sh.
It looks like nano's post-install/-deinstall requires print/indexinfo
and it's not available. This doesn'
Re:
<https://lists.freebsd.org/archives/freebsd-pkgbase/2025-May/000516.html>
<https://www.reddit.com/r/freebsd/comments/1khf860/comment/mr6o8ke/> has
two screenshots that compare the 14.2-RELEASE experience (good) with the
15.0-CURRENT experience.
It seems that /bin/tcsh no
Steffen Nurpmeso wrote:
> You know the entire thread is moot as i think bapt@ has thrown
> away the BSD termcap years ago, if i recall correctly (i think
> i spoke up by then).
> I only answered because of the "great it is gone" thing.
Maybe I should have rephrased that as "it's great that we on
Hello Thomas Dickey.
Thomas Dickey wrote in
:
|On Thu, Nov 02, 2023 at 06:58:55PM +0100, Steffen Nurpmeso wrote:
|> I do understand that a bit. Other than that plain termcap was so
|> small and i would assume essentially unchanged for decades, that
|> i do not. Termcap entries, yes. I coul
On Thu, Nov 02, 2023 at 06:58:55PM +0100, Steffen Nurpmeso wrote:
> I do understand that a bit. Other than that plain termcap was so
> small and i would assume essentially unchanged for decades, that
> i do not. Termcap entries, yes. I could imagine vt220, xterm,
> screen-256color, and take one
Steffen Nurpmeso wrote:
> Why?
> (That is to say: why -- if it is a *real* termcap? If it is only
> a translation layer to terminfo, i am with you. But otherwise
> not, i think a real termcap is much, much smaller, while offering
> anything a (simple) console program needs.)
> That is not to ta
f
> you want another behaviour and larger support you install terminfo-db.
>
> The fact that tcsh does not play nicely with terminfo, is nother problem.
Thanks for the clarification. I had mistakingly thought many things pulled in
terminfo-db, but it appears to be only deskutils/arttime
On Wed, Nov 01, 2023 at 03:49:33AM +, Jamie Landeg-Jones wrote:
> Thomas Dickey wrote:
>
> > actually it probably does affect "xterm"
> >
> > Checking the source, tcsh is expecting a termcap string, while data read
> > from the terminfo database is g
Thomas Dickey wrote:
> actually it probably does affect "xterm"
>
> Checking the source, tcsh is expecting a termcap string, while data read
> from the terminfo database is going to be in terminfo format -- even if
> read via tgetent/tgetstr
>
> tcsh is expecti
On Tue, Oct 31, 2023 at 10:59:48PM +, Jamie Landeg-Jones wrote:
> Jamie Landeg-Jones wrote:
>
> > switch to tcsh, and reinitialise terminal information:
> >
> > % setenv TERM dumb
> > % setenv TERM xterm
>
> % setenv TERM xterm-256color
>
> Apo
Jamie Landeg-Jones wrote:
> switch to tcsh, and reinitialise terminal information:
>
> % setenv TERM dumb
> % setenv TERM xterm
% setenv TERM xterm-256color
Apologies, it seems this doesn't affect plain "xterm", but it does at least
affect xterm-16color and xterm-25
Hi!
The changes to FreeBSD base ncurses to use the terminfo db over termcap if it
exists have caused a few issues with tcsh, which doesn't seem to grok terminfo.
e.g. : install misc-terminfo
switch to tcsh, and reinitialise terminal information:
% setenv TERM dumb
% setenv TERM xterm
% e
Something that would creating a nice messaging system like in c++ or maybe objc
that would be transparent to hardware to end user
I have some sample code of a mdmdbt on https://unidef.net
Sent from my iPhone
___
freebsd-current@freebsd.org mailing list
On 10 May 2013 16:59, Ronald F. Guilmette wrote:
>
> http://www.freebsd.org/cgi/query-pr.cgi?pr=bin/152154
>
> It has been suggested to me (by a committer) that I should raise the
> issue of this PR here on these lists, because the problem described
> within the PR remains a real problem, and desp
In message <20130510213610.gg8...@home.opsec.eu>, you wrote:
>> http://www.freebsd.org/cgi/query-pr.cgi?pr=bin/152154
>>
>> It has been suggested to me (by a committer) that I should raise the
>> issue of this PR here on these lists, because the problem described
>> within the PR remains a real
http://www.freebsd.org/cgi/query-pr.cgi?pr=bin/152154
It has been suggested to me (by a committer) that I should raise the
issue of this PR here on these lists, because the problem described
within the PR remains a real problem, and despite my having proposed
something that seems to be a perfectl
Hi!
> http://www.freebsd.org/cgi/query-pr.cgi?pr=bin/152154
>
> It has been suggested to me (by a committer) that I should raise the
> issue of this PR here on these lists, because the problem described
> within the PR remains a real problem, and despite my having proposed
> something that seems
and
didn't know anything about shell's possibilities. Somebody recommends me
bash and I used it as my default shell for a couple of years - until I
realized, that same or better prompt, completion and history search can
be achieved with already installed csh / tcsh. Just by few modifi
> + set autoexpand
>
> No one complained about this - it is almost certainly going to stay
> it the final version.
>
> Now to address some comments made in the thread. I'm sorry for not
> preserving attribution here.
>
>> How about adding stuff like this to
On 10/02/2012 17:25, Eitan Adler wrote:
> setenv BLOCKSIZE K
Why note BLOCKSIZE M? It's pretty much ridiculous to count kilobytes
nowadays.
> Many people had alternative suggestions for the prompt. Can you please
> clarify why you believe your prompt should be the _default_ one?
My promp
On Tue, Feb 14, 2012 at 7:26 AM, Eitan Adler wrote:
> On Tue, Feb 14, 2012 at 8:19 AM, Astrodog wrote:
>> Personally, I pay very little attention to the prompt. That being said...
>> Plenty of people prefer widely different configurations for the prompt.
>> I think everyone agrees that the defaul
On Tue, Feb 14, 2012 at 8:19 AM, Astrodog wrote:
> Personally, I pay very little attention to the prompt. That being said...
> Plenty of people prefer widely different configurations for the prompt.
> I think everyone agrees that the default prompt isn't particularly
> informative, however, achiev
x27; must have everyone.
PAGER is not necessary.
And this is best prompt I think =)
--
View this message in context:
http://freebsd.1045724.n5.nabble.com/Enhancing-the-user-experience-with-tcsh-tp5471144p5481784.html
Sent from the freebsd-current mail
Chris Rees wrote:
set prompt = "[%n@%m]%c04%# "
it's not needed
need some as
alias ll ls -lAhG
alias ls ls -G
Lscolors are an abomination. -F or nothing at all is better; remember some
people will use white xterms etc.
Yeah, a +1 for me. Plain xterm with colorized output m
Alex Keda wrote:
On 10.02.2012 21:07, Chuck Burns wrote:
set prompt = "[%n@%m]%c04%# "
it's not needed
need some as
alias ll ls -lAhG
alias ls ls -G
set autolist = TAB
bindkey "\e[3~" delete-char
.
and other _really_ necessary settings
This can be as simple as defining CLICOLOR. Howe
On Sun, Feb 12, 2012 at 2:16 PM, Chris Rees wrote:
>
> On 12 Feb 2012 17:11, "Chuck Swiger" wrote:
>>
>> On Feb 11, 2012, at 11:05 PM, Gonzalo Nemmi wrote:
>> > Joel, with all due respect, do you really think that 99.9% of all
>> > users will not find the _non_intrusive_ additions below useful?
>
les. Far too much of what people consider obvious
improvements
> not only do not apply everywhere, they sometimes *don't* *work* and break
> things.
Right... not once however have you referenced the Home/End/Delete keys,
which is what I was talking about (I'll give you Insert) :)
On Feb 12, 2012, at 9:16 AM, Chris Rees wrote:
> So do I, but would these hurt you?
At the present time, no. (At one point, I was using a keyboard
where the arrow keys generated "ESC-[ 1 ~" through "4",
IIRC, but I haven't been on console on it in some time.)
> I think it's insane that by defaul
> including them so all users get to have a fully functional keyboard by
> default.
I think this kind of basic stuff should work without any configuration;
it should be fixed in the tcsh code if it does not work already.
It looks like Home and End already work in the common configura
On 12 Feb 2012 17:11, "Chuck Swiger" wrote:
>
> On Feb 11, 2012, at 11:05 PM, Gonzalo Nemmi wrote:
> > Joel, with all due respect, do you really think that 99.9% of all
> > users will not find the _non_intrusive_ additions below useful?
> >
> > bindkey "\e[1~" beginning-of-line #make Home key work
On Feb 11, 2012, at 11:05 PM, Gonzalo Nemmi wrote:
> Joel, with all due respect, do you really think that 99.9% of all
> users will not find the _non_intrusive_ additions below useful?
>
> bindkey "\e[1~" beginning-of-line #make Home key work;
> bindkey "\e[2~" overwrite-mode #make Ins key work;
>
> How about adding stuff like this to
/usr/share/examples/tcsh/complete.tcsh ?
>
> --
> Joel
Yes to that.
This is exactly where these suggestions should go.
Feel free to create multiple examples files there but be very carefully
with changes to system w
4,8 +24,10 @@
> # An interactive shell -- set some stuff up
> set prompt = "`/bin/hostname -s`# "
> set filec
> - set history = 100
> - set savehist = 100
> + set history = 1000
> + set savehist = (1000 mer
@
>> > # An interactive shell -- set some stuff up
>> > set prompt = "`/bin/hostname -s`# "
>> > set filec
>> > - set history = 100
>> > - set savehist = 100
>> > + set history = 1000
>
gt; set filec
> > - set history = 100
> > - set savehist = 100
> > + set history = 1000
> > + set savehist = (1000 merge)
> > + set autolist
> > + set autoexpand
> > set mail = (/var/mail/$USER)
> > if
set prompt = "`/bin/hostname -s`# "
set filec
- set history = 100
- set savehist = 100
+ set history = 1000
+ set savehist = (1000 merge)
+ set autolist
+ set autoexpand
set mail = (/var/mail/$USER)
if ( $?tcsh ) then
set history = 100
- set savehist = 100
+ set history = 1000
+ set savehist = (1000 merge)
+ set autolist
+ set autoexpand
set mail = (/var/mail/$USER)
if ( $?tcsh ) then
bindkey "^W" backward-delete-word
Also,
On Friday, 10th February 2012, Eitan Adler wrote:
>-alias la ls -a
>+alias la ls -aF
> alias lf ls -FA
>-alias ll ls -lA
>+alias ll ls -lAF
>+alias ls ls -F
>
>Two people didn't like these changes but didn't explain why. This is
>incredibly helpful, especially f
on 11/02/2012 00:29 Chuck Swiger said the following:
> On Feb 10, 2012, at 2:12 PM, Andriy Gapon wrote:
>> I really hate the default behavior of less where you can't quit via ^C or via
>> paging through the end of file.
>
> It's readily tunable, by setenv'ing LESS variable to contain some of:
>
>
t some stuff up
> set prompt = "`/bin/hostname -s`# "
> set filec
> - set history = 100
> - set savehist = 100
> + set history = 1
> + set savehist = 10000
> + set autolist
> + # Use history to aid expansion
> + set au
On Feb 10, 2012, at 2:12 PM, Andriy Gapon wrote:
> I really hate the default behavior of less where you can't quit via ^C or via
> paging through the end of file.
It's readily tunable, by setenv'ing LESS variable to contain some of:
-e or --quit-at-eof
Causes less to automat
[cc list trimmed]
on 10/02/2012 18:25 Eitan Adler said the following:
[snip]
> set path = (/sbin /bin /usr/sbin /usr/bin /usr/games /usr/local/sbin
> /usr/local/bin $HOME/bin)
>
> setenv EDITOR vi
> -setenv PAGER more
> +setenv PAGER less
> setenv BLOCKSIZE K
> No one complained ab
On 10 Feb 2012 19:41, "Alex Keda" wrote:
>
> On 10.02.2012 21:07, Chuck Burns wrote:
>>
>> set prompt = "[%n@%m]%c04%# "
>
> it's not needed
>
> need some as
> alias ll ls -lAhG
> alias ls ls -G
Lscolors are an abomination. -F or nothing at all is better; remember some
people wil
On 10.02.2012 21:07, Chuck Burns wrote:
set prompt = "[%n@%m]%c04%# "
it's not needed
need some as
alias ll ls -lAhG
alias ls ls -G
set autolist = TAB
bindkey "\e[3~" delete-char
and other _really_ necessary settings
> complete chown 'p/1/u/'
> complete man
Am 10.02.2012 17:41, schrieb Gavin Atkinson:
> On Fri, 2012-02-10 at 11:25 -0500, Eitan Adler wrote:
>> Picking a random email to reply to.
>>
>> My goal with this email is to reduce the amount of "controversial" changes.
>
> I applaud this. I've often considered doing the same but avoided it
> b
; > + set autolist
> > + # Use history to aid expansion
> > + set autoexpand
> > set mail = (/var/mail/$USER)
> > if ( $?tcsh ) then
> > bindkey "^W" backward-delete-word
> > bindkey -k up history-search-backward
it to $PATH if it
> > exists, but that has nothing to do with ".cshrc should be updated for
> > modern hardware" ... it jsut comes in really handy.
>
> The question becomes "how much is too much?" For example, ever since a
> thread in the forums showed exa
On Fri, Feb 10, 2012 at 11:41 PM, Gavin Atkinson
wrote:
> This change is disruptive, and it can affect use of ls(1) in scripts.
Scripts never use alias and...
> For example, it even sticks the extra characters in the output of
> "ls -1" (the number 1), which is specifically designed to be used w
On Fri, Feb 10, 2012 at 9:07 AM, Chuck Burns wrote:
> On 2/10/2012 10:41 AM, Gavin Atkinson wrote:
>>
>> On Fri, 2012-02-10 at 11:25 -0500, Eitan Adler wrote:
>>>
>>> Picking a random email to reply to.
>>>
>>> My goal with this email is to reduce the amount of "controversial"
>>> changes.
>>
>> I
On 2/10/2012 10:41 AM, Gavin Atkinson wrote:
On Fri, 2012-02-10 at 11:25 -0500, Eitan Adler wrote:
Picking a random email to reply to.
My goal with this email is to reduce the amount of "controversial" changes.
I applaud this. I've often considered doing the same but avoided it
because it was
On Fri, 2012-02-10 at 11:25 -0500, Eitan Adler wrote:
> Picking a random email to reply to.
>
> My goal with this email is to reduce the amount of "controversial" changes.
I applaud this. I've often considered doing the same but avoided it
because it was easier than fighting the bikeshed :)
> c
t certainly going to stay
it the final version.
Now to address some comments made in the thread. I'm sorry for not
preserving attribution here.
> How about adding stuff like this to /usr/share/examples/tcsh/complete.tcsh ?
> Along with a comment in .cshrc pointing to that file (or even
/$USER)
if ( $?tcsh ) then
bindkey "^W" backward-delete-word
bindkey -k up history-search-backward
bindkey -k down history-search-forward
endif
+ set prompt = "[%n@%m]%c04%# "
+ set promptchars = "%#"
g to
> > be non-annoying to the vast majority of users. I'd like feedback about
> > the specific patch I proposed. We can also create a wiki page for
> > more awesome tcsh examples.
> >
> > For the record this is the current version of the patch I'd like to
it'd be better for this to be "set autolist=ambiguous" - it
changes an accidental keypress into a deliberate choice, and matches
Linux a bit better.
> + # Use history to aid expansion
> + set autoexpand
> set mail = (/var/mail/$USER)
> if ( $?tcs
On Fri, 10 Feb 2012, Joel Dahl wrote:
[completion examples]
How about adding stuff like this to /usr/share/examples/tcsh/complete.tcsh ?
Along with a comment in .cshrc pointing to that file (or even a
commented line to source it), it would be an improvement. People who
can benefit the
also create a wiki page for
> more awesome tcsh examples.
>
> For the record this is the current version of the patch I'd like to
> commit: Note that it slightly changed from the original (I removed the
> duplicate prompt setup and reorganized where
ed by what is someone else's amazing setup
>
> The changes I proposed were designed to add value while continuing to
> be non-annoying to the vast majority of users. I'd like feedback about
> the specific patch I proposed. We can also create a wiki page for
> more awesome
is is: novice user don't know how to enable some
"advanced" settings for default FreeBSD shell (csh / tcsh) or even don't
know they exist. But all skilled persons are able to disable "annoing"
new settings in few seconds.
I think that default FreeBSD install should be
value while continuing to
be non-annoying to the vast majority of users. I'd like feedback about
the specific patch I proposed. We can also create a wiki page for
more awesome tcsh examples.
For the record this is the current version of the patch I'd like to
commit: Note that it slightly c
Hi,
On Friday 10 February 2012 19:36:29 Alexander Leidinger wrote:
> Quoting Miroslav Lachman <000.f...@quip.cz> (from Fri, 10 Feb 2012
> 12:05:59 +0100):
>
> > I would like to share them with others, if there are interrest to
> > include it in stock FreeBSD base.
>
> If there's no interest,
Quoting Miroslav Lachman <000.f...@quip.cz> (from Fri, 10 Feb 2012
12:05:59 +0100):
I would like to share them with others, if there are interrest to
include it in stock FreeBSD base.
If there's no interest, or no consent to add a specific one, why not
collect them in a wiki-page?
Bye,
> > exists, but that has nothing to do with ".cshrc should be updated for
> > modern hardware" ... it jsut comes in really handy.
>
> The question becomes "how much is too much?" For example, ever since a
> thread in the forums showed examples of csh/tcsh auto
will always be helpful for beginners and
also for people like me who use BSD since years but did not see certain options
tcsh has.
OK, here it is http://freebsd.quip.cz/ext/2012/2012-02-10-tcshrc/
It is based on tcshrc files found on the net, so it is not all my work.
The files include many
ast here. It will always be helpful for beginners and
also for people like me who use BSD since years but did not see certain options
tcsh has.
Erich
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-curre
Hi,
On Friday 10 February 2012 13:50:06 Warren Block wrote:
> On Fri, 10 Feb 2012, Gonzalo Nemmi wrote:
>
> > On Thu, Feb 9, 2012 at 9:52 PM, Eitan Adler wrote:
> >> In conf/160689 (http://www.freebsd.org/cgi/query-pr.cgi?pr=160689)
>
> The question becomes "how much is too much?" For example,
"how much is too much?" For example, ever since a
thread in the forums showed examples of csh/tcsh autocompletion, I've
thought the default .cshrc should be stuffed with them. Not for typing
reduction so much as self-documenting commands like
complete chown 'p/1/u/'
complete man
> If tcsh could be updated to version 6.18.00 "set autorehash" would be
> really nice. With that you'll never have to type "rehash" again. :)
Yes please!
Steinar Haug, Nethelp consulting, sth...@nethelp.no
___
freebsd-c
at the end of the thread. This post is an attempt to open the change
> to wider discussion.
If tcsh could be updated to version 6.18.00 "set autorehash" would be
really nice. With that you'll never have to type "rehash" again. :)
--
Homepage: www.yamagi.o
On Thu, Feb 9, 2012 at 6:52 PM, Eitan Adler wrote:
> In conf/160689 (http://www.freebsd.org/cgi/query-pr.cgi?pr=160689)
> there has been some discussion about changing the default cshrc file.
>
> I'd like to commit something like the following based on Chris's patch
> at the end of the thread. Th
On 09-02-2012 19:52, Eitan Adler wrote:
> In conf/160689 (http://www.freebsd.org/cgi/query-pr.cgi?pr=160689)
> there has been some discussion about changing the default cshrc file.
>
> I'd like to commit something like the following based on Chris's patch
> at the end of the thread. This post is a
h?" For example, ever since a
thread in the forums showed examples of csh/tcsh autocompletion, I've
thought the default .cshrc should be stuffed with them. Not for typing
reduction so much as self-documenting commands like
complete chown 'p/1/u/'
complete man
An interactive shell -- set some stuff up
> set prompt = "`/bin/hostname -s`# "
> set filec
> - set history = 100
> - set savehist = 100
> + set history = 1
> + set savehist = 10000
> + set autolist
> + # Use history to a
ll -- set some stuff up
> set prompt = "`/bin/hostname -s`# "
> set filec
> - set history = 100
> - set savehist = 100
> + set history = 1
> + set savehist = 1
> + set autolist
> + # Use history to aid ex
m# "
endif
> set filec
> - set history = 100
> - set savehist = 100
> + set history = 1
> + set savehist = 1
> + set autolist
set autologout = 0
> + # Use history to aid expansion
> + set autoexpand
>
Do the promptchars work correctly on csh as well as tcsh?
Adrian
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
tolist
+ # Use history to aid expansion
+ set autoexpand
set mail = (/var/mail/$USER)
if ( $?tcsh ) then
bindkey "^W" backward-delete-word
bindkey -k up history-search-backward
bindkey -k down history-search-for
Greetings,
I have recently posted a possible patch which seems to solve a malfunction
that occurs with the script(1) program when it is used with the -k option
and certain shells which allow for command line editing.
The patch may be send towards the (current) end of the discussion regarding
thi
John-Mark Gurney wrote:
> Tim Kientzle wrote this message on Wed, Jun 25, 2003 at 09:51 -0700:
> > Why do exec-ed processes inherit the children of the former
> > process, anyway? That doesn't entirely sound right to me.
> > Is that behavior mandated by some standard? If not, this
> > could argua
Tim Kientzle wrote this message on Wed, Jun 25, 2003 at 09:51 -0700:
[...]
> >Say the shell you run the above command is 10. It will fork to create
> >a shell to run the commands in the outter parens. Call this 11. 11's
> >job is to run: (echo 2; echo 3) | ./xargs -I% echo +%
> >11 will fork/e
Tim J. Robbins wrote this message on Wed, Jun 25, 2003 at 19:20 +1000:
> On Wed, Jun 25, 2003 at 12:41:51AM -0700, John-Mark Gurney wrote:
>
> [...]
> > So, now the question is, do we fix xargs to deal with unexpected
> > children? Or fix the shells in question? (tcsh a
stion is, do we fix xargs to deal with unexpected
children? Or fix the shells in question? (tcsh and zsh seem to suffer
this problem)
To me, fixing xargs is correct since it prevents another possible
future abusers of this "feature".
Good work! Congratulations on figuring that one o
John-Mark Gurney wrote:
> So, now the question is, do we fix xargs to deal with unexpected
> children? Or fix the shells in question? (tcsh and zsh seem to suffer
> this problem)
>
> To me, fixing xargs is correct since it prevents another possible
> future abusers of this
On Wed, Jun 25, 2003 at 12:41:51AM -0700, John-Mark Gurney wrote:
[...]
> So, now the question is, do we fix xargs to deal with unexpected
> children? Or fix the shells in question? (tcsh and zsh seem to suffer
> this problem)
>
> To me, fixing xargs is correct since it p
the first proccess
has exited, run the second echo command. Due to scheduling, we'll
have two processes running at the same time which can cause the
interleaving of data.
So, now the question is, do we fix xargs to deal with unexpected
children? Or fix the shells in question? (tcsh and
Juli Mallett wrote this message on Wed, Jun 25, 2003 at 00:15 -0500:
> * Juli Mallett <[EMAIL PROTECTED]> [ Date: 2003-06-24 ]
> [ w.r.t. Re: tcsh being dodgy, or pipe code ishoos? ]
> > * Tim Kientzle <[EMAIL PROTECTED]> [ Date: 2003-06-24 ]
> > > Hmmm... Th
* Juli Mallett <[EMAIL PROTECTED]> [ Date: 2003-06-24 ]
[ w.r.t. Re: tcsh being dodgy, or pipe code ishoos? ]
> * Tim Kientzle <[EMAIL PROTECTED]> [ Date: 2003-06-24 ]
> > Hmmm... This looks like xargs isn't waiting for the subcommand
> > to exit. This lo
* Tim Kientzle <[EMAIL PROTECTED]> [ Date: 2003-06-24 ]
[ w.r.t. Re: tcsh being dodgy, or pipe code ishoos? ]
> Artem 'Zazoobr' Ignatjev wrote:
> > Juli Mallett wrote:
> >
> >>Anyone with insight into this?
> >>
> >>([EMAIL PR
d it's more weird than that:
> >
> >>( echo 1 ; ( ( echo 2 ; echo 3 ) | xargs -I% echo -- + % ) )
> >
> >1
> >-- --+ +2
> >3
> >
>
>
> Hmmm... This looks like xargs isn't waiting for the subcommand
> to exit. This looks like &#x
Artem 'Zazoobr' Ignatjev wrote:
Juli Mallett wrote:
Anyone with insight into this?
([EMAIL PROTECTED]:~)39% ( echo 1 ; ( ( echo 2 ; echo 3 ) | xargs -I% echo + % ) )
1
+ 2
+ 3
([EMAIL PROTECTED]:~)40% ( echo 1 ; ( ( echo 2 ; echo 3 ) | xargs -I% echo + % ) ) |
cat
1
+ +2
3
last cat is not necess
jmallett> Anyone with insight into this?
"Me Too" with zsh 4.0.6 on 5-current as of early June/2003.
-- -
Makoto `MAR' Matsushita
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail
On Tue, Jun 24, 2003 at 18:54:11 -0500, Juli Mallett wrote:
> stdout. Where does stderr come into it? Yes I know about TTY races
Forget about stderr, it looks like fork race somewhere. Minimal example
will be
( ( echo 2 ; echo 3 ) | xargs -I% echo + % )
which outputs
+ + 3
2
in rare cases.
Juli Mallett wrote:
> Anyone with insight into this?
>
> ([EMAIL PROTECTED]:~)39% ( echo 1 ; ( ( echo 2 ; echo 3 ) | xargs -I% echo + % ) )
> 1
> + 2
> + 3
> ([EMAIL PROTECTED]:~)40% ( echo 1 ; ( ( echo 2 ; echo 3 ) | xargs -I% echo + % ) ) |
> cat
> 1
> + +2
> 3
last cat is not necessary...
And
* Andrey Chernov <[EMAIL PROTECTED]> [ Date: 2003-06-24 ]
[ w.r.t. Re: tcsh being dodgy, or pipe code ishoos? ]
> On Tue, Jun 24, 2003 at 18:35:15 -0500, Juli Mallett wrote:
> > Anyone with insight into this?
> >
> > ([EMAIL PROTECTED]:~)39% ( echo 1 ; ( ( e
On Tue, Jun 24, 2003 at 18:35:15 -0500, Juli Mallett wrote:
> Anyone with insight into this?
>
> ([EMAIL PROTECTED]:~)39% ( echo 1 ; ( ( echo 2 ; echo 3 ) | xargs -I% echo + % ) )
> 1
> + 2
> + 3
Loks like stdout/stderr mix, but I not check the code, so just raw guess.
__
Anyone with insight into this?
([EMAIL PROTECTED]:~)39% ( echo 1 ; ( ( echo 2 ; echo 3 ) | xargs -I% echo + % ) )
1
+ 2
+ 3
([EMAIL PROTECTED]:~)40% ( echo 1 ; ( ( echo 2 ; echo 3 ) | xargs -I% echo + % ) ) |
cat
1
+ +2
3
([EMAIL PROTECTED]:~)41% ( echo 1 ; ( ( echo 2 ; echo 3 ) | xargs -I% echo
On Sun, Oct 06, 2002 at 04:10:55PM -0700, Kris Kennaway wrote:
> Can anyone else reproduce this in tcsh?
>
> rpcgen -s `perl -e 'print "a"x5'`
> Word too long.
I reported this to the tcsh people about 18 months ago, but I
don't think it was ever fixed.
On 06-Oct-2002 (23:10:55/GMT) Kris Kennaway wrote:
> Can anyone else reproduce this in tcsh?
> rpcgen -s `perl -e 'print "a"x5'`
> Word too long.
Mee too mail. Using {50,500,5000} works, hang only with 5
(not tested with others numbers). Doing:
# echo {y
Michael Nottebrock wrote:
> Kris Kennaway wrote:
>
>> Can anyone else reproduce this in tcsh?
>
>
> Yup. My -CURRENT here is two weeks old.
... reproducible in -STABLE, too.
Regards,
--
Michael Nottebrock
"And the reasons? There are no reasons."
msg4413
1 - 100 of 190 matches
Mail list logo
