On Fri, Dec 10, 2010 at 05:24:34AM EST, Marc Herbert wrote:
> > It's trivial to write a shell function to do that, and many other
> > things.
>
> Things like "good default settings" and "batteries included"
Not sure the reference to python (?) is relevant here, since the
language by itself does
On Mon, Feb 21, 2011 at 04:13:54AM EST, Marcel de Reuver wrote:
> In a bash script I use: $[`date --date='this week' +'%V'`%2] to see if
> the week number is even.
> Only in week 08 the error is: bash: 08: value too great for base
> (error token is "08") the same in week 09, all others are ok...
On Thu, Dec 22, 2011 at 01:09:38PM EST, Peng Yu wrote:
> Hi,
> As I mentioned previously, there are shortcomings in man bash. Here,
> I just point another example. And I hope my suggestion will be
> addressed.
[..]
Here's my suggestion, and nothing needs to be ‘addressed’.
There are shortcomin
On Sat, Dec 24, 2011 at 10:08:31AM EST, Bill Gradwohl wrote:
[..]
> The man page is written the way Robbie the Robot used to speak in the old
> black and white TV days¹. Short, cryptic and in many cases unintelligible IN
> THE DETAILS. Alternatively, one might snicker that some lawyer wrote it to
On Mon, Jan 23, 2012 at 08:52:17AM EST, Roger wrote:
[..]
> Matter of fact, I'm starting to find VIM's long wait time length
> a little annoying. ;-)
:h tm
:h ttm
CJ
On Mon, Jan 23, 2012 at 07:38:52PM EST, Chet Ramey wrote:
> On 1/23/12 8:52 AM, Roger wrote:
>
> > A little more indepth examination, and I can see VIM's wait is
> > approximately double of what the readline patch's wait time is.
> > However, I think the shorter wait time is more functional as whe
On Sat, Mar 21, 2009 at 01:01:51PM EDT, Cam Cope wrote:
> I'm sorry if the feature has already been implemented, I haven't heard
> of any way to implement it. This is what I was thinking of: Right now,
> if you run history, it will list out all the recently used commands,
> and then you could run
On Sat, Mar 21, 2009 at 01:16:12PM EDT, Ken Irving wrote:
> This sounds a lot like what you get with the reverse-search-history
> command, bound to control-r (C-r), a great feature indeed.
Priceless.
I had posted the following obfuscated explanation a couple of hours ago
but since I was subscr
On Sat, Mar 21, 2009 at 04:59:36PM EDT, Bob Proulx wrote:
> Chris Jones wrote:
> > I had posted the following obfuscated explanation a couple of hours
> > ago but since I was subscribed under a different address, it never
> > made it to the list.
> >
> > :-(
&g
Not sure whether this is a bug in my version of bash, but I copied over
my colored PS1 prompts from debian etch - regular user & root - and some
convenient keyboard actions are misbehaving. After retrieving a command
from the history via a CTRL-R, an ensuing CTRL-A moves the cursor to
somewhere in
Not sure whether this is a bug in my version of bash, but I copied over
my colored PS1 prompts from debian etch - regular user & root - and some
convenient keyboard actions are misbehaving. After retrieving a command
from the history via a CTRL-R, an ensuing CTRL-A moves the cursor to
somewhere in
On Tue, Jun 30, 2009 at 05:23:27AM EDT, Bernd Eggink wrote:
> Chris Jones schrieb:
>> ...
> > After retrieving a command
>> from the history via a CTRL-R, an ensuing CTRL-A moves the cursor to
>> somewhere in the middle of the prompt and CTRL-E is short of the
>>
On Tue, Jun 30, 2009 at 08:30:35AM EDT, Chet Ramey wrote:
> Chris Jones wrote:
> > Not sure whether this is a bug in my version of bash, but I copied over
> > my colored PS1 prompts from debian etch - regular user & root - and some
> > convenient keyboard actions are misb
On Tue, Jun 30, 2009 at 01:34:21PM EDT, Chet Ramey wrote:
> Chris Jones wrote:
[..]
> > Is there anything that happened between 3.2.39 & 3.2.49 that might
> > account for this, or would you suspect a problem with my setup?
>
> I would assume that one of the patches addr
Configuration Information [Automatically generated, do not change]:
Machine: i486
OS: linux-gnu
Compiler: gcc
Compilation CFLAGS: -DPROGRAM='bash' -DCONF_HOSTTYPE='i486'
-DCONF_OSTYPE='linux-gnu' -DCONF_MACHTYPE='i486-pc-linux-gnu'
-DCONF_VENDOR='pc' -DLOCALEDIR='/usr/share/locale' -DPACKAGE='ba
On Sat, Jul 04, 2009 at 12:18:51PM EDT, Chris Jones wrote:
> Configuration Information [Automatically generated, do not change]:
> Machine: i486
> OS: linux-gnu
> Compiler: gcc
> Compilation CFLAGS: -DPROGRAM='bash' -DCONF_HOSTTYPE='i486'
> -DCONF_OSTYP
On Sat, Jul 04, 2009 at 02:56:20PM EDT, Chet Ramey wrote:
[..]
> Thanks for the report. I can reproduce this on bash-3.2.49, and it's
> fixed in bash-4.0.
Thanks for confirming I was not hearing voices or something :-)
Is there a 4.0 .deb available..?
I just compiled:
http://ftp.gnu.org/gn
On Sat, Jul 04, 2009 at 11:20:56PM EDT, Bob Proulx wrote:
> Chris Jones wrote:
> > Is there a 4.0 .deb available..?
> A bash 4.0 .deb is available in Debian's experimental distribution. I
> don't know if the dependencies it was compiled with are available in
> Lenny o
On Fri, Jul 17, 2009 at 04:54:51PM EDT, Dave B wrote:
> On Friday 17 July 2009, Linda Walsh wrote:
>
> > where does the output from the 'time' command "go"
> >
> > I.e. if I wanted to pipe the output to a prog or file, how would I
> > go about doing it?
>
> Please see
>
> http://mywiki.wooledge.
On Thu, Jan 28, 2010 at 08:42:25PM EST, Clark J. Wang wrote:
> Hi all,
> I want to write my own built-in bash commands but I cannot find any
> info about that in bash manual. Anyone has any idea?
Never done that myself but I found this excellent introductory article:
http://cfajohnson.com/shell
20 matches
Mail list logo