Configuration Information [Automatically generated, do not change]:
Machine: i686
OS: linux-gnu
Compiler: gcc
Compilation CFLAGS: -DPROGRAM='bash' -DCONF_HOSTTYPE='i686'
-DCONF_OSTYPE='linux-gnu' -DCONF_MACHTYPE='i686-redhat-linux-gnu'
-DCONF_VENDOR='redhat' -DLOCALEDIR='/usr/share/locale' -DPAC
Those two URLs are the same!
--
Ryan Cunningham
> On Mar 1, 2015, at 1:28 AM, Jonathan Hadida
> wrote:
>
> Hi there
>
> There is a dead link in the online bash manual for shopt:
> http://www.gnu.org/software/bash/manual/html_node/The-Shopt-Builtin.html
> [prom
This issue has nothing to do with Bash. It is likely an artifact of the Ubuntu
terminal driver.
Try e-mailing the Ubuntu developers or Canonical Ltd. for help. They may
provide a solution.
--
Sent from my iPod
> On Feb 24, 2015, at 2:15 PM, Steve Terpe wrote:
>
> This seems to be related to
All right, maybe I can discuss it with the right people when I have the time.
But for now, let's stop the discussion here.
--
Sent from my iPod
> On Jan 27, 2015, at 7:46 AM, Eduardo A. Bustamante López
> wrote:
>
>> On Tue, Jan 27, 2015 at 06:11:37AM -0800, Ryan Cunning
And by "type-in programs" in the message to which I am replying, I mean those
published in source code form.
--
Sent from my iPod
> On Jan 26, 2015, at 10:19 PM, Ryan Cunningham wrote:
>
> These type-in programs can actually generate quicker rises in popularity of
>
/Linux's market share
could potentially beat Microsoft Windows' (which is actually what the FSF hopes
will happen, with "Upgrade from Windows 8").
--
Sent from my iPod
> On Jan 26, 2015, at 4:12 PM, Ryan Cunningham wrote:
>
> I would also like the discussion on the
who reads
these messages to spread the word about the idea.
--
Sent from my iPod
> On Jan 26, 2015, at 3:50 PM, Ryan Cunningham wrote:
>
> No, no, not on the Internet---I mean in a paper magazine, which Internet
> users can also get.
>
> I'd like the machine code discussio
No, no, not on the Internet---I mean in a paper magazine, which Internet users
can also get.
I'd like the machine code discussion to end.
--
Sent from my iPod
On Jan 26, 2015, at 3:03 PM, Eduardo A. Bustamante López
wrote:
>> I am proposing this as a possible alternative or complement to pu
6, 2015 at 01:32:21PM -0800, Ryan Cunningham wrote:
> > When you receive a program in *object code* form, you would type it into
> an
> > object code editor and then save it in a binary file.
>
> Why? Is it 1982 again? Are we typing in 6502 machine code from a
> glossy ma
tuff. Bash interpretes *source code*, it doesn't matter
> how you
> provide it. The only exception is what Greg specified.
>
--
Ryan Cunningham
And that is exactly what I mean---running a separate program. Sorry for any
confusion.
On Mon, Jan 26, 2015 at 10:43 AM, Greg Wooledge wrote:
> On Mon, Jan 26, 2015 at 10:36:37AM -0800, Ryan Cunningham wrote:
> > I mean that the program would be loaded in the same manner in which Bas
015, at 10:25 AM, Greg Wooledge wrote:
>
>> On Mon, Jan 26, 2015 at 10:14:19AM -0800, Ryan Cunningham wrote:
>> Sorry, I forgot to state that it could also be saved by an object code
>> editor and loaded then like you would load any other program in object code.
>
> B
On Jan 26, 2015, at 8:35 AM, Ryan Cunningham wrote:
> These requirements only dictate how the code is provided. They dictate that
> source code must somehow be provided, even if the program is published in
> object code form; how it must be provided; and other additional requirement
And, by the way, the here-document is source code; what you type into that
editor (in hexadecimal, decimal, or octal form) is object code already compiled.
--
Sent from my iPod
> On Jan 26, 2015, at 9:07 AM, Ryan Cunningham wrote:
>
> A here-document isn't object code; I mean o
A here-document isn't object code; I mean object code you edit in the editor
provided in or referenced by the aggregate and /then/ execute after it has been
saved, like you would save a plain text file.
--
Sent from my iPod
On Jan 26, 2015, at 9:05 AM, Eduardo A. Bustamante López
wrote:
>>
> On Jan 26, 2015, at 8:18 AM, Chet Ramey wrote:
[. . .]
> Do you intend to say that this should affect how the `Type-In' addendum to
> the GPL is written or interpreted? If so, how is it different from any
> publishing requirements that exist on a shell script?
These requirements only dictat
--
Sent from my iPad
>> On Nov 23, 2014, at 11:29 AM, Ryan Cunningham wrote:
>>
>> On Nov 23, 2014, at 10:58 AM, Chet Ramey wrote:
>>
>> -BEGIN PGP SIGNED MESSAGE-
>> Hash: SHA1
>>
>>> On 11/21/14 9:31 PM, Eric Blake wrote:
&g
On Nov 23, 2014, at 10:58 AM, Chet Ramey wrote:
>
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
>> On 11/21/14 9:31 PM, Eric Blake wrote:
>>
>> $ bash --debugger foo
>> bash: debug script /usr/bin/bashdb: file not found
>>
>> to give me a heads up that I need to install bashdb. Would it
Configuration Information [Automatically generated, do not change]:
Machine: x86_64
OS: darwin14.0.0
Compiler: gcc
Compilation CFLAGS: -DPROGRAM='bash' -DCONF_HOSTTYPE='x86_64'
-DCONF_OSTYPE='darwin14.0.0' -DCONF_MACHTYPE='x86_64-apple-darwin14.0.0'
-DCONF_VENDOR='apple' -DLOCALEDIR='/usr/local/
Sorry---I misunderstood.
Sent from my iPod
On Oct 31, 2014, at 6:40 PM, Ryan Cunningham wrote:
> On Oct 31, 2014, at 6:12 PM, jon wrote:
>
>> Maybe it should be more like this:
>>
>> # time
>> Error, 'time' with no arguments is only meaningful in pos
On Oct 31, 2014, at 6:12 PM, jon wrote:
> Maybe it should be more like this:
>
> # time
> Error, 'time' with no arguments is only meaningful in posix mode
Or maybe like this (to be more like the standard BASH error format):
bash: time: an argument is required (POSIX mode enabled)
Sent from my
Thank you for the clarification.
--
Sent from my iPad
> On Oct 6, 2014, at 4:12 AM, Chet Ramey wrote:
>
>> On 10/5/14, 9:45 PM, Ryan Cunningham wrote:
>> This patch contains statements that add references to the patch directory,
>> "bash-4.3-patched". Yo
This patch contains statements that add references to the patch directory,
"bash-4.3-patched". You should reissue the patch without such statements if you
find it feasible to do so.
--
Sent from my iPad
> On Oct 5, 2014, at 4:06 PM, Chet Ramey wrote:
>
> BASH PATCH REPORT
>
Maybe BASH should instead output "$'\r'" in the error message in your case.
--
Sent from my iPad
> On Sep 10, 2014, at 1:58 AM, Vincent Lefevre wrote:
>
> In error messages, raw non-printable characters from arguments should
> not be output without transformation, at least if this is on a term
This isn't clear to me. Are you using the Almquist Shell to execute BASH to run
your script, or is BASH already running when the script is executed?
--
Sent from my iPad
> On Sep 8, 2014, at 1:17 AM, Jan Rome wrote:
>
> Hello,
>
> I'd like to report an obscure bug I came across in pfsense wh
According to Dennis's e-mail, this is normal behavior, not a bug. Do not
attempt to fix it.
--
Sent from my iPad
> On Jun 4, 2014, at 2:02 PM, Jens Stimpfle wrote:
>
>> On Wed, Jun 04, 2014 at 01:34:22PM -0600, Eric Blake wrote:
>> On 06/04/2014 01:28 PM, Dennis Williamson wrote:
My feel
Apparently I am not reading it wrong. Read my previous e-mail to this list on
this thread.
Sent from my iPad
> On Mar 1, 2014, at 8:55 PM, Chris Down wrote:
>
>> On 2014-03-01 11:29:03 -0800, Dave Yost wrote:
>> In http://www.gnu.org/software/bash/manual/bashref.html#GNU-Parallel
>>
>> Where
Hmmm. That doesn't seem right. Actually, the original statement is correct.
Sent from my iPad
> On Mar 1, 2014, at 11:29 AM, Dave Yost wrote:
>
> In http://www.gnu.org/software/bash/manual/bashref.html#GNU-Parallel
>
> Where you say
> ls *.gz | parallel -j+0 "zcat {} | bzip2 >{.}.bz2 && rm {}"
z
tar -xzvf bash-4.3.tar.gz
cd bash-4.3
./configure --prefix=/ --datarootdir=/usr/share --sharedstatedir=/usr/com
--includedir=/usr/include
make
make install
cd ..
rm -rf bash-4.3
exit
Sent from my iPad
> On Mar 1, 2014, at 2:13 PM, Yuri wrote:
>
>> On 03/01/2014 14:07, Ryan Cunnin
You could use the command "history -c" to clear the history in case this
becomes a real issue. I don't have a real fix.
Sent from my iPad
> On Mar 1, 2014, at 1:23 PM, Yuri wrote:
>
> I manipulate with some files containing UTF8 characters. The only commands I
> run are these:
> ./some-cmd <
do-filter' calls;
but do not post the complete script).
Sincerely,
Ryan Cunningham
Sent from my iPad
> On Dec 11, 2013, at 1:13 AM, Yuri wrote:
>
>> On 12/11/2013 01:04, Piotr Grzybowski wrote:
>> hullo,
>>
>> maybe post exact scripts that generate those
Also, as a correction to your original message, a FIFO _is_ a file, just not a
regular file.
Sent from my iPad
> On Dec 11, 2013, at 1:13 AM, Yuri wrote:
>
>> On 12/11/2013 01:04, Piotr Grzybowski wrote:
>> hullo,
>>
>> maybe post exact scripts that generate those files, together with
>> som
Thank you. I will therefore change my mind and suggest this feature _not_ be
included.
(I could also try
$ stty kill '@'
for the same reason.)
Sent from my iPad
> On Nov 25, 2013, at 4:09 PM, Bob Proulx wrote:
>
> Ryan Campbell Cunningham wrote:
>>I would like to request that Bash d
33 matches
Mail list logo
