On Tue, 02 Jan 2018 04:33:56 +0100, Stephan Beal
wrote:
(this time back to the list)
On Tue, Jan 2, 2018 at 3:43 AM, Andy Bradford
wrote:
Thus said Stephan Beal on Tue, 02 Jan 2018 03:07:20 +0100:
> That will still strip any newlines
Thus said Stephan Beal on Tue, 02 Jan 2018 04:33:56 +0100:
> That's not what i'm seeing:
>
> [stephan@host:~]$ echo -e "1\n2\n3"
> 1
> 2
> 3
> [stephan@host:~]$ echo $(echo -e "1\n2\n3")
> 1 2 3
Hmm, that's interesting. Have a look at this... Here's a file that has
newlines in it, and which
Stephan,
You need to quote the argument to "echo", otherwise the whitespace
is collapsed by the shell.
For example:
echo "$(echo -e "1\n2\n3")"
On Tue, 2 Jan 2018, Stephan Beal wrote:
(this time back to the list)
On Tue, Jan 2, 2018 at 3:43 AM, Andy Bradford
(this time back to the list)
On Tue, Jan 2, 2018 at 3:43 AM, Andy Bradford
wrote:
> Thus said Stephan Beal on Tue, 02 Jan 2018 03:07:20 +0100:
>
> > That will still strip any newlines from his input, though, because
> > that's how $(...) works.
>
> It actually only
Thus said Stephan Beal on Tue, 02 Jan 2018 03:07:20 +0100:
> That will still strip any newlines from his input, though, because
> that's how $(...) works.
It actually only strips the trailing newline. Any newlines in the middle
of the file are fine. So for example:
$ cat third.txt
Third
On Tue, Jan 2, 2018 at 2:25 AM, Ron W wrote:
> Try splitting the long text file into 2 or more smaller files, then add
> the ticket using the first file. Then you can append to the comment:
>
>$ fossil ticket change TICKETUUID +comment "$(cat content_next)"
>
That will
On Mon, Jan 1, 2018 at 6:48 PM,
wrote:
> Date: Mon, 01 Jan 2018 12:44:42 +
> From: Sergey Bronnikov
> Subject: [fossil-users] ticket length limitation
>
> For most by bugs it works fine, but command is failed when ticket body
>
7 matches
Mail list logo