Re: documentation bug re character range expressions

2011-06-13 Thread Andre Majorel
On 2011-06-09 12:40 -0700, Marcel (Felix) Giannelia wrote: > Guess it's time I really learned how to navigate texinfo... You can spare yourself the pain with something along the lines of #!/bin/sh info --subnodes -o- "$1" | less (Which won't help you in this particular case as neither bash nor

Re: Built-in printf Sits Awkwardly with UDP.

2011-07-21 Thread Andre Majorel
On 2011-07-20 14:34 +0100, Ralph Corderoy wrote: > No. Here's my understanding of how it currently works. The built-in > printf works out a character to print at a time; no foresight needed or > used. It asks the C library to print it with putchar(3). The C library > can implement buffering t

Readline : move to previous/next path component

2008-10-14 Thread Andre Majorel
One frequently needed function that readline does not seem to have is a way to move to the beginning of the next or previous path component. This is what I've come up with : \C-t: "\C-b\C-b\e\C-]/\C-f" \C-y: "\C-]/\C-f" Three problems with this kludge : 1. The definition uses keys, not funct

Re: Readline : move to previous/next path component

2008-10-15 Thread Andre Majorel
On 2008-10-15, Chet Ramey <[EMAIL PROTECTED]> wrote: > Andre Majorel wrote: >> One frequently needed function that readline does not seem to >> have is a way to move to the beginning of the next or previous >> path component. > > Readline doesn't have any buil

Re: Readline : move to previous/next path component

2008-10-15 Thread Andre Majorel
On 2008-10-15, Chet Ramey <[EMAIL PROTECTED]> wrote: >> On 2008-10-15, Chet Ramey <[EMAIL PROTECTED]> wrote: >> > Andre Majorel wrote: >> >> One frequently needed function that readline does not seem to >> >> have is a way to move to the beg

Re: Readline : move to previous/next path component

2008-10-16 Thread Andre Majorel
On 2008-10-16, Aharon Robbins <[EMAIL PROTECTED]> wrote: > In article <[EMAIL PROTECTED]>, > Andre Majorel <[EMAIL PROTECTED]> wrote: >>Vi mode would help, but in Bash, there's no way to switch >>between it and Emacs mode on the fly. > > Au contrair

Re: Readline : move to previous/next path component

2008-10-17 Thread Andre Majorel
On 2008-10-16, Larry Clapp <[EMAIL PROTECTED]> wrote: > On Thu, Oct 16, 2008 at 09:12:23AM +0000, Andre Majorel wrote: >> On 2008-10-16, Aharon Robbins <[EMAIL PROTECTED]> wrote: >> > In article <[EMAIL PROTECTED]>, >> > Andre Majorel <[EMAIL PR

Issuing re-read-init-file from a Bash function

2010-08-10 Thread Andre Majorel
How do you force a reload of ~/.inputrc from a Bash function ? All "bind re-read-init-file" seems to do is make the [f] key go away. Thanks in advance. -- André Majorel http://www.teaser.fr/~amajorel/

Verbatim pasting

2010-08-10 Thread Andre Majorel
Binding printable ASCII characters to readline functions is convenient but it can bite you when you paste text into a shell. Is there a way to bypass readline while pasting ? Something like a ^V toggle or a ^V that lasts until the next newline or next pause between two characters longer than 250 m

Re: Verbatim pasting

2010-08-10 Thread Andre Majorel
On 2010-08-10 16:05 -0400, Mike Frysinger wrote: > On Tue, Aug 10, 2010 at 2:08 PM, Andre Majorel wrote: > > Binding printable ASCII characters to readline functions is > > convenient but it can bite you when you paste text into a shell. > > > > Is there a way to by

Re: \c escape within $'...' can produce mangled UTF-8

2010-08-14 Thread Andre Majorel
On 2010-08-15 01:08 +0400, Dmitry Groshev wrote: > If an escape's parameter makes no sense, escape sequence should be > left untranslated - just the way "\x" handles things like "\xZZ". Make > "\c" check that its parameter is an ASCII char, and the problem will > be fixed. > Unless for some reason

Re: Encoding multiple filenames in a single variable

2010-08-29 Thread Andre Majorel
On 2010-08-29 17:12 +1000, Jon Seymour wrote: > This isn't strictly a bash question, and I'd prefer a POSIX-only > solution if possible [ suggestions as to a good question to ask > POSIX-only questions would be appreciated ]. comp.unix.shell > Suppose I need to encode a list of filenames in a va

Re: asking for a better way to implement this

2010-09-27 Thread Andre Majorel
On 2010-09-27 18:39 +0200, Christopher Roy Bratusek wrote: > I'm using GNU/Linux for seven years now, it's now almost > impossible to learn to use `xrm' instead of `rm'. Put rm(){su} in your .bashrc. You'll be surprised. :-> -- André Majorel http://www.teaser.fr/~amajorel/

syntax error near unexpected token `time'

2014-12-14 Thread Andre Majorel
Funny one : $ bash -c 'echo a | time cat' a [/usr/bin/time output deleted] On the other hand : $ bash -c 'echo a | time cat' bash: -c: line 1: syntax error near unexpected token `time' bash: -c: line 1: `time cat' [$PS2 deleted] Dash, ksh and zsh accept either form. That was wi

Re: syntax error near unexpected token `time'

2014-12-15 Thread Andre Majorel
On 2014-12-14 21:12 -0500, Chet Ramey wrote: > Yes, `time' should not be recognized as a reserved word in this case, even > though the previous token is a newline. I'll take a look at it. Thanks > for the report. Note that the error occurs even if there is white space between the newline and "t