Re: [PATCH] stty doc enhancements
All good except: PB> How about: PB> These settings control operations on data received from the terminal. PB> These settings control operations on data sent to the terminal. Remember that you need to locate the user between the two ends of something... One can't just imply. In each sentence you need to say what is the part nearest to them and what part is farthest from them somehow. Thanks. ___ Bug-coreutils mailing list Bug-coreutils@gnu.org http://lists.gnu.org/mailman/listinfo/bug-coreutils
Re: [PATCH] stty doc enhancements
The clarifications are worthwhile though a little verbose.
comments below..
jida...@jidanni.org wrote:
> ---
> doc/coreutils.texi | 12 +---
> 1 files changed, 9 insertions(+), 3 deletions(-)
>
> diff --git a/doc/coreutils.texi b/doc/coreutils.texi
> index 49aa16d..020dc51 100644
> --- a/doc/coreutils.texi
> +++ b/doc/coreutils.texi
> @@ -11919,6 +11919,8 @@ Enable RTS/CTS flow control. n...@acronym{posix}.
> May be negated.
> @subsection Input settings
>
> @cindex input settings
> +These arguments specify input-related operations, i.e., bytes sent
> +from your terminal to the computer are affected by them.
How about:
These settings control operations on data received from the terminal.
>
> @table @samp
> @item ignbrk
> @@ -11991,7 +11993,9 @@ empty again. May be negated.
> @opindex iuclc
> @cindex uppercase, translating to lowercase
> Translate uppercase characters to lowercase. n...@acronym{posix}. May be
> -negated.
> +negated. (Note no ilcuc is currently implemented, probably because one
> +would not be able to use any more Unix commands, which are almost all
> +lower case, after invoking it.)
How about:
Note no ilcuc is implemented, as one would not be able to issue
almost any (lowercase) Unix command, after invoking it.
>
> @item ixany
> @opindex ixany
> @@ -12010,7 +12014,8 @@ when the input buffer is full. n...@acronym{posix}.
> May be negated.
> @subsection Output settings
>
> @cindex output settings
> -These arguments specify output-related operations.
> +These arguments specify output-related operations, i.e., bytes sent
> +from the computer to your terminal are affected by them.
How about:
These settings control operations on data sent to the terminal.
>
> @table @samp
> @item opost
> @@ -12021,7 +12026,7 @@ Postprocess output. May be negated.
> @opindex olcuc
> @cindex lowercase, translating to output
> Translate lowercase characters to uppercase. n...@acronym{posix}. May be
> -negated.
> +negated. (Note no ouclc is currently implemented.)
>
> @item ocrnl
> @opindex ocrnl
> @@ -12274,6 +12279,7 @@ as @code{tab3}.
> @opindex lcase
> @opindex LCASE
> Same as @code{xcase iuclc olcuc}. n...@acronym{posix}. May be negated.
> +(Note no ucase has been implemented.)
How about just saying:
(Used for terminals with uppercase characters only.)
thanks for persevering with this,
Pádraig.
___
Bug-coreutils mailing list
Bug-coreutils@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-coreutils
[PATCH] stty doc enhancements
---
doc/coreutils.texi | 12 +---
1 files changed, 9 insertions(+), 3 deletions(-)
diff --git a/doc/coreutils.texi b/doc/coreutils.texi
index 49aa16d..020dc51 100644
--- a/doc/coreutils.texi
+++ b/doc/coreutils.texi
@@ -11919,6 +11919,8 @@ Enable RTS/CTS flow control. n...@acronym{posix}. May
be negated.
@subsection Input settings
@cindex input settings
+These arguments specify input-related operations, i.e., bytes sent
+from your terminal to the computer are affected by them.
@table @samp
@item ignbrk
@@ -11991,7 +11993,9 @@ empty again. May be negated.
@opindex iuclc
@cindex uppercase, translating to lowercase
Translate uppercase characters to lowercase. n...@acronym{posix}. May be
-negated.
+negated. (Note no ilcuc is currently implemented, probably because one
+would not be able to use any more Unix commands, which are almost all
+lower case, after invoking it.)
@item ixany
@opindex ixany
@@ -12010,7 +12014,8 @@ when the input buffer is full. n...@acronym{posix}.
May be negated.
@subsection Output settings
@cindex output settings
-These arguments specify output-related operations.
+These arguments specify output-related operations, i.e., bytes sent
+from the computer to your terminal are affected by them.
@table @samp
@item opost
@@ -12021,7 +12026,7 @@ Postprocess output. May be negated.
@opindex olcuc
@cindex lowercase, translating to output
Translate lowercase characters to uppercase. n...@acronym{posix}. May be
-negated.
+negated. (Note no ouclc is currently implemented.)
@item ocrnl
@opindex ocrnl
@@ -12274,6 +12279,7 @@ as @code{tab3}.
@opindex lcase
@opindex LCASE
Same as @code{xcase iuclc olcuc}. n...@acronym{posix}. May be negated.
+(Note no ucase has been implemented.)
@item crt
@opindex crt
--
1.5.6.5
___
Bug-coreutils mailing list
Bug-coreutils@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-coreutils
Re: Ubuntu 8.10 CD Image
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 [please keep the list in the loop, and avoid top-posting] According to Al Jorge on 12/17/2008 12:22 PM: > Hi Erik: It's Eric, but that's okay > > > > After recent Ubuntu releases there have been several people who have > > been asking about Ubuntu questions on this GNU Coreutils mailing > > list. If you would be so kind could you tell us what has directed you > > to ask your question on this mailing list? We fear that there may be > > incorrect documentation pointing you here. If you would help us so > > that we could improve the directions it would help others. Thanks! > > I do not recall where I found the link in question... Oh well, thanks for replying. - -- Don't work too hard, make some time for fun as well! Eric Blake e...@byu.net -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (Cygwin) Comment: Public key at home.comcast.net/~ericblake/eblake.gpg Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAklJXbMACgkQ84KuGfSFAYDKGACffbfEzJihOQGbawBzpu4iG0SI T/AAoK65mecx+yQ6CpTYa9UgPJuhyEPH =rn7M -END PGP SIGNATURE- ___ Bug-coreutils mailing list Bug-coreutils@gnu.org http://lists.gnu.org/mailman/listinfo/bug-coreutils
Re: wc command
chakrapani.chittabathina wrote: > Hi, > First, we are grateful to you for your contribution towards this great > open source project. > Bug : when i am using "wc" command, i've entered only wc without any > option and file name even, acidently, then it didn't give any error > report, even not giving help info. wc reads from standard input if no file is specified. So it was patiently waiting for you to type something. >And, i found one thing about CentOS, it is little bit slow compare to > windows which is running in he same hardware. That's a little vague/offtopic :) Pádraig. ___ Bug-coreutils mailing list Bug-coreutils@gnu.org http://lists.gnu.org/mailman/listinfo/bug-coreutils
Re: wc command
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 According to chakrapani.chittabathina on 12/17/2008 1:06 AM: Hello Chakrapani, > Bug : when i am using "wc" command, i've entered only wc without any > option and file name even, acidently, then it didn't give any error > report, even not giving help info. This is not a bug, but expected behavior. When you don't provide any arguments, wc acts as a filter, and counts the words input on stdin. In your case, stdin is the terminal where you entered the command, so wc is now waiting for you to type words, followed by the terminal's end-of-file sequence (typically Ctrl-D). This applies not only to wc, but to many of the coreutils; it sounds like you are a bit unfamiliar with the Unix paradigm of tools that act as filters when not given a file name to act upon. >And, i found one thing about CentOS, it is little bit slow compare to > windows which is running in he same hardware. That would be an issue with CentOS, not coreutils. In turn, Windows is very slow compared to Linux running in the same hardware, not to mention that GNU/Linux systems give you more freedoms than a proprietary OS. > DISCLAIMER: The information in this message is confidential As a note of netiquette, these sorts of disclaimers are unenforceable on publicly archived mailing lists. However, some people refuse to reply to mail where a trailer like this has been inserted. Therefore, you may want to consider using a different account when mailing bug reports. - -- Don't work too hard, make some time for fun as well! Eric Blake e...@byu.net -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (Cygwin) Comment: Public key at home.comcast.net/~ericblake/eblake.gpg Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAklI+KAACgkQ84KuGfSFAYC7ogCgzGpFUAVifbjtFNs5wJekxnA8 47sAnjJjyiu4Tg3qk0GVEV6WVtAmA+Hp =JnFs -END PGP SIGNATURE- ___ Bug-coreutils mailing list Bug-coreutils@gnu.org http://lists.gnu.org/mailman/listinfo/bug-coreutils
wc command
Hi, First, we are grateful to you for your contribution towards this great open source project. Bug : when i am using "wc" command, i've entered only wc without any option and file name even, acidently, then it didn't give any error report, even not giving help info. And, i found one thing about CentOS, it is little bit slow compare to windows which is running in he same hardware. Regards, Chakrapani.Ch == DISCLAIMER: The information in this message is confidential and may be legally privileged. It is intended solely for the addressee. Access to this message by anyone else is unauthorized. If you are not the intended recipient, any disclosure, copying, or distribution of the message, or any action or omission taken by you in reliance on it, is prohibited and may be unlawful. Please immediately contact the sender if you have received this message in error. Further, this e-mail may contain viruses and all reasonable precaution to minimize the risk arising there from is taken by OnMobile. OnMobile is not liable for any damage sustained by you as a result of any virus in this e-mail. All applicable virus checks should be carried out by you before opening this e-mail or any attachment thereto. Thank you - OnMobile Global Limited. == ___ Bug-coreutils mailing list Bug-coreutils@gnu.org http://lists.gnu.org/mailman/listinfo/bug-coreutils
Re: problem finding mktemp in info file
Pádraig Brady wrote: > Stepan Kasal wrote: >> >> In short, shell code snippets shall use \(aq for single quotes and \` >> for the "backticks" > > Excellent, thanks! > > I'm thinking of pushing the attached. > > I'll wait at least until your mail hits the coreutils archives. > bug-coreutils@gnu.org seems mega slow at the moment? That looks fine to me, since that the du use is the only thing other than "info" suggestions: $ grep "'" man/*.1|grep -F .B|grep -v invoca man/du.1:.B du --exclude='*.o' Thanks! ___ Bug-coreutils mailing list Bug-coreutils@gnu.org http://lists.gnu.org/mailman/listinfo/bug-coreutils
Re: problem finding mktemp in info file
Stepan Kasal wrote: > > In short, shell code snippets shall use \(aq for single quotes and \` > for the "backticks" Excellent, thanks! I'm thinking of pushing the attached. I'll wait at least until your mail hits the coreutils archives. bug-coreutils@gnu.org seems mega slow at the moment? Pádraig. >From 4000c35ae3546aca05ece49ffa01ba2a763000b0 Mon Sep 17 00:00:00 2001 From: =?utf-8?q?P=C3=A1draig=20Brady?= Date: Wed, 17 Dec 2008 10:41:34 + Subject: [PATCH] doc: Remove curly quotes from shell examples in man pages Use \(aq rather than a literal ' as groff will convert apostrophe to a right quote (\u2029) in utf8 locales for example. Stepan Kasal details the issue and fix here: http://lists.gnu.org/archive/html/bug-coreutils/2008-12/msg00124.html --- man/du.x |2 +- man/help2man |2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/man/du.x b/man/du.x index b170369..85b9ff4 100644 --- a/man/du.x +++ b/man/du.x @@ -19,7 +19,7 @@ will match any files whose names end in .BR .o . Therefore, the command .IP -.B du --exclude='*.o' +.B du --exclude=\(aq*.o\(aq .PP will skip all files and subdirectories ending in .BR .o diff --git a/man/help2man b/man/help2man index cbdaf06..66d715f 100755 --- a/man/help2man +++ b/man/help2man @@ -567,7 +567,7 @@ and .B %s programs are properly installed at your site, the command .IP -.B info coreutils '%s invocation' +.B info coreutils \(aq%s invocation\(aq .PP should give you access to the complete manual. EOT -- 1.5.3.6 ___ Bug-coreutils mailing list Bug-coreutils@gnu.org http://lists.gnu.org/mailman/listinfo/bug-coreutils
Re: problem finding mktemp in info file
Hello Padraig, On Wed, Dec 17, 2008 at 12:15:11AM +, Pádraig Brady wrote: > Is there any way to markup example code so that > 'blah' is not converted to ’blah’ ? indeed, that is very confusing and the groff man pages (at least the versions in recent Fedora) are not accurate. Contrary to popular belief, several ASCII characters do not represent themselves in the roff source. These are not only escape characters (backslash, dot in first column, apostrophe as parameter delimiter). Such characters include ' (apostrophe) and ` (greve accent, often used as left quote). This list may or may not be complete, I don't know. Here is the markup table (result of my experiments with groff): ' \(cq right quote \' \(aa accute accent \(aqapostrophe (ASCII 0x27) ` \(oq left quote \` \(ga greve accent (ASCII 0x60) The three without ASCII code listed are characters not present ion ASCII, so in an Unicode locale, the code point (or what's that Unicode-speak term) is >= 256. If you are using a C locale, or an locale with ISO-8859-x encoding, these Unicode characters may not be available, so a substitute character is used, and the bug is masked. In short, shell code snippets shall use \(aq for single quotes and \` for the "backticks" (the official name of that ASCII character is "greve accent"---it seems weird to have an accented space character in ASCII, but that's how things stay). See also http://bugzilla.redhat.com/471025 Have a nice day, Stepan Kasal ___ Bug-coreutils mailing list Bug-coreutils@gnu.org http://lists.gnu.org/mailman/listinfo/bug-coreutils
