Re: Why tclsh use "\r\n" for return values in Unix?
- From: "tom.rmadilo" <tom.rmadilo@xxxxxxxxx>
- Date: Thu, 29 Oct 2009 16:03:39 -0700 (PDT)
On Oct 29, 2:14 pm, Don Porter <d...@xxxxxxxx> wrote:
pmarin wrote:
Why in Unix the tclsh return the values ending with "\r\n"
Setting aside my confusion about your exact scenario, try this command
fconfigure stdout -translation lf
and see if it configures things more to your liking.
But just to be clear for anyone else who stumbles across this thread:
the problem must be with the "acme editor" or some kind of
configuration mix-up. By default Tcl uses the line ending sequence for
the host platform. On "unix" that is "\n".
You also can't always trust your editor to display text correctly.
.
- Follow-Ups:
- Re: Why tclsh use "\r\n" for return values in Unix?
- From: pmarin
- Re: Why tclsh use "\r\n" for return values in Unix?
- References:
- Why tclsh use "\r\n" for return values in Unix?
- From: pmarin
- Re: Why tclsh use "\r\n" for return values in Unix?
- From: Don Porter
- Why tclsh use "\r\n" for return values in Unix?
- Prev by Date: tclkit wonder
- Next by Date: Re: How to act on a widget if clicked outside of it?
- Previous by thread: Re: Why tclsh use "\r\n" for return values in Unix?
- Next by thread: Re: Why tclsh use "\r\n" for return values in Unix?
- Index(es):