These commands are launched just after the adding my current user 'ostap' to
the 'root' 'cvs' groups. So I have noticed 2 unconjectured things:
1. If I add me (user 'ostap') to some groups, it is not very convenient to
logout login every time. As far as I can see, this is a kernel restriction
Hi *,
Yes, it does, but this feature is pain ass to enter on a bash-shell:
Absolutely. And this bothers me in many respects, not just
with sort -t. Perhaps you should be directing your bug
reports to the Bash maintainer. After all, in this
particular context (and in the other contexts I'm
A very odd bug, when a call the comand:
date --date=2006-10-15
this give me a invalid date.
This happens only in that specific date 2006-10-15, very strange. Look
below.
cged057:~$ date --date=2004-02-27
Fri Feb 27 00:00:00 BRT 2004
cged057:~$ date --date=2006-10-15
date: invalid date
On Mon, 11 Dec 2006, [EMAIL PROTECTED] wrote:
A very odd bug, when a call the comand:
date --date=2006-10-15
this give me a invalid date.
This happens only in that specific date 2006-10-15, very strange. Look
below.
I assume from your email address and BRT timezone that you're in the
Ostap Kutsyy wrote:
These commands are launched just after the adding my current user 'ostap' to
the 'root' 'cvs' groups. So I have noticed 2 unconjectured things:
1. If I add me (user 'ostap') to some groups, it is not very convenient to
logout login every time. As far as I can see,
Philip Rowlands [EMAIL PROTECTED] writes:
I can't reproduce this. Here's what I get with the
tzdata-2006p-1.fc5 installed on Fedora Core 5:
$ export TZ=Brazil/East
$ date --date=2006-10-15
Sun Oct 15 00:00:00 BRT 2006
I can reproduce the problem on Debian stable (with coreutils 6.7 date)
[EMAIL PROTECTED] writes:
A very odd bug, when a call the comand:
date --date=2006-10-15
this give me a invalid date.
This happens only in that specific date 2006-10-15, very strange. Look
below.
cged057:~$ date --date=2004-02-27
Fri Feb 27 00:00:00 BRT 2004
cged057:~$ date
(Sorry this isn't exactly the right list, but this feels like a problem
coreutils should solve, and I don't see gmane carrying anything better.)
I am looking for a way to convert binary data to a format that 'printf'
will understand (and more importantly, from which 'something | sed
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to DI Oliver Maurhart on 12/11/2006 1:03 AM:
No. Actually the $'\t' works! It's pretty cool. I'm into Linux for
several years now, but everyday you get surprised by such small goodies.
Didn't know of that one.
Both bash and zsh support
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Matthew Woehlke on 12/11/2006 5:46 PM:
The objective is to be able to reproduce a binary file from an 'editor
friendly' shell script. I know base64 could do this, except that base64
is not portable (even to pre-6.x GNU coreutils),
Hi,
Well, yes, maybe. To insert a tab on a console based on simultaneously
pressing a combination of several keys on the keyboard ... gee, tab:
bash-completion, alt-tab: whhoppp there it goes I'm in my second app
on the desktop, ctrl-tab: w, I'm in yet another desktop ...
Okay, just so
Please take a look at thread:
http://lists.pld-linux.org/mailman/pipermail/pld-devel-en/2006-December/018341.html
The problem is that coreutils uses own internal copies
of openat() and fchmodat() even if glibc already provides
these functions (starting from glibc 2.4).
Simplest patch:
diff
Matthew Woehlke wrote:
I am looking for a way to convert binary data to a format that 'printf'
will understand (and more importantly, from which 'something | sed
's/\\//g' | xargs printf' will produce the same output as the
input). Am I missing such a utility, or might this be an
Arkadiusz Miskiewicz [EMAIL PROTECTED] writes:
Please take a look at thread:
http://lists.pld-linux.org/mailman/pipermail/pld-devel-en/2006-December/018341.html
The problem is that coreutils uses own internal copies
of openat() and fchmodat() even if glibc already provides
these functions
Eric Blake wrote:
Ctrl-V is pretty much the standard default in UNIX terminals for quoting
the next character typed, which means the sequence [ctrl-v] then [tab] is
almost universally accepted, regardless of whether you use bash, ksh, ash,
or even csh. With ctrl-v, it is the terminal doing
DI Oliver Maurhart wrote:
The question is solely: does sort support it or not. And
currently it simply doesn't. That's all.
Several people have already posted examples showing that quoting tab
for use with sort as a delimiter does work okay.
Bob
Paul Eggert [EMAIL PROTECTED] wrote:
How about the following patch instead? It seems a bit more
straightforward. However, I don't fully understand the problem so I
may well have gotten it wrong.
2006-12-11 Paul Eggert [EMAIL PROTECTED]
* m4/openat.m4 (gl_FUNC_OPENAT): Don't
Jim Meyering [EMAIL PROTECTED] writes:
That looks fine to me.
OK, I installed it into gnulib.
___
Bug-coreutils mailing list
Bug-coreutils@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-coreutils
18 matches
Mail list logo
