Some interesting posts, I don't think it's directly related to systemd but the
mentality is not far off. Some developer likes the feature so everyone should
have it because that one developer likes it. Maybe most users won't complain,
but I bet those users won't be the ones who use the shell oft
Aldemir Akpinar writes:
[...]
> http://lists.gnu.org/archive/html/coreutils/2016-02/msg00026.html
For the sake of factual accuracy: As far as publically know, nobody ever
sent death threats to Lennart Poettering because of an opinion on system
differing from his own. At some point in time in th
On 19 February 2016 at 05:11, dev1fanboy wrote:
> Little late to this thread, that sounds like annoying default behaviour
> and more of this same mentality that breaking backwards compatibility is
> OK, it's really not at all. Really it should be the other way, set -N to
> use the new wrapping. B
Little late to this thread, that sounds like annoying default behaviour and
more of this same mentality that breaking backwards compatibility is OK, it's
really not at all. Really it should be the other way, set -N to use the new
wrapping. But hey why not right, systemd does this so we should to
Revision 8.25-2 disables default quoting now.
Mitt
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
On Tuesday, 16 February 2016, Steve Litt wrote:
> On Tue, 16 Feb 2016 16:07:35 +0200
> Aldemir Akpinar > wrote:
>
>
> My response is unresponsive to your question, aldemir, but this is
> something I've given lots of thought to in the past. I quote from the
> referenced web page:
>
> =
>Pipes and files.
Oh, aye, how could I forget this :(
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Mitt Green writes:
This lad, Pádraig, says, that it happens only
when outputting to terminals. I wonder,
where else you can output ls.
Pipes and files. This outputs to a pipe:
ls | grep X
This outputs to a slightly different pipe:
for a in $(ls) ...
This outputs to a file:
ls > /tmp/
Mitt Green writes:
> Adam Borowski wrote:
[...]
>>script names: no.
>>C/Pascal/COBOL sources: no.
>>mp3/videos/ebooks/etc: hell yes.
>
> [...]
>
>>The change is breaking valid use cases.
>
> I definitely understand the indignation,
> yet I can't imagine cases, where mp3/ebooks/
> et al. are us
Adam Borowski wrote:
>The relevant bug is
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=813164
This lad, Pádraig, says, that it happens only
when outputting to terminals. I wonder,
where else you can output ls.
And surely, pasting this back to anywhere,
the result will be the same: unwanted
Adam Borowski wrote:
>script names: no.
>C/Pascal/COBOL sources: no.
>mp3/videos/ebooks/etc: hell yes.
[...]
>The change is breaking valid use cases.
I definitely understand the indignation,
yet I can't imagine cases, where mp3/ebooks/
et al. are used in scripts.
>The relevant bug is
>https:
On Tue, Feb 16, 2016 at 07:51:47PM +0300, Mitt Green wrote:
> No idea, why they did it,
> but anyway, who uses whitespaces in
> names of scripts? I always get
> rid of them even when naming
> wallpapers.
script names: no.
C/Pascal/COBOL sources: no.
mp3/videos/ebooks/etc: hell yes.
The change is
On Tue, 16 Feb 2016 16:07:35 +0200
Aldemir Akpinar wrote:
> There's a recent discussion on the coreutils mailing list, where some
> people complained about the default ls output with latest release. On
> coreutils 8.25 ls will wrap filenames with quotes if it includes
> whitespace.
>
> And when
Emiliano Marini writes:
For example, this willl break scripts parsig ls output.
Will it?
I spent a few minutes looking for scripts that might be broken. I did find
one that acted on ls output, but it wasn't broken.
Arnt
___
Dng mailing list
Dng@l
No idea, why they did it,
but anyway, who uses whitespaces in
names of scripts? I always get
rid of them even when naming
wallpapers.
Mitt
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Aldemir Akpinar writes:
[...]
>> BTW: 'Console' and 'terminal' are two rather different things.
>>
>>
> Doesn't your init scripts run on the console?
'The system console' is an I/O device the kernel and scripts started
during boot will use for "user interaction", ie, print output supposed
to be
Arnt Gulbrandsen writes:
> Emiliano Marini writes:
>> Great Scott! Introducing unwanted changes in packages containing the
>> word "core", congratulations!
>>
>> This will break up 99% of the scripts out there...
>
> Why?
>
> This won't break common code such as
>
> for a in *.xml; do
> ...
For example, this willl break scripts parsig ls output.
On Tue, Feb 16, 2016 at 12:52 PM, Arnt Gulbrandsen wrote:
> Emiliano Marini writes:
>
>> Great Scott! Introducing unwanted changes in packages containing the word
>> "core", congratulations!
>>
>> This will break up 99% of the scripts out t
Emiliano Marini writes:
Great Scott! Introducing unwanted changes in packages
containing the word "core", congratulations!
This will break up 99% of the scripts out there...
Why?
This won't break common code such as
for a in *.xml; do
...
What it breaks is rubbish such as
for a i
>
>
> Hmm ... why do you think so?
>
> BTW: 'Console' and 'terminal' are two rather different things.
>
>
Doesn't your init scripts run on the console? Or the scripts that run on
the initial ram disk. Please correct me if I am wrong.
--
aldemir
___
Dng m
Aldemir Akpinar writes:
[...]
> On coreutils 8.25 ls will wrap filenames with quotes if it includes
> whitespace.
>
> And when people protest, the answers are usual arguments; it just happens
> on the console output, or just add -N to your aliases etc. etc.
[...]
> When this version hits the d
Am Dienstag, 16. Februar 2016 schrieb Aldemir Akpinar:
> There's a recent discussion on the coreutils mailing list, where some
> people complained about the default ls output with latest release. On
> coreutils 8.25 ls will wrap filenames with quotes if it includes
> whitespace.
>
> And when peopl
Great Scott! Introducing unwanted changes in packages containing the word
"core", congratulations!
This will break up 99% of the scripts out there...
On Tue, Feb 16, 2016 at 11:07 AM, Aldemir Akpinar wrote:
> There's a recent discussion on the coreutils mailing list, where some
> people complai
There's a recent discussion on the coreutils mailing list, where some
people complained about the default ls output with latest release. On
coreutils 8.25 ls will wrap filenames with quotes if it includes
whitespace.
And when people protest, the answers are usual arguments; it just happens
on the
24 matches
Mail list logo
