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 contraire:
set -o vi
set -o emacs
--
Aharon (Arnold) Robbins arnold AT sk
RMMM wrote:
RMMM wrote:
As far as I can tell, the variables $filenames and $filenames1 have the
same values. Yet, they
behave differently when used in an argument. Is there some hidden aspect
to a bash variable
that I'm not seeing?
I just figured out the problem. I was running this in a shel
RMMM wrote:
>
> As far as I can tell, the variables $filenames and $filenames1 have the
> same values. Yet, they
> behave differently when used in an argument. Is there some hidden aspect
> to a bash variable
> that I'm not seeing?
>
I just figured out the problem. I was running this in a sh
I'm trying to create a bash function for use in auto completion, but
I've run into bash behavior I don't understand. All I want to do is
generate a list of the file names from a certain directory. I have a line
filenames=$(for file in `ls -1 mydir`; do echo -n "${file} " ; done )
This seems to p
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 beginning of the next or previous
>> >> path component.
>> >
> last_made_pid != last_pid)
> {
> ...
> exec_result = wait_for (last_made_pid);
> }
>
> I'm wondering why we are doing assignment (last_pid = last_made_pid;)
> and then test it (&& last_made_pid != last_pid)?
To see if we created a process in execu
> 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 built-in knowledge of Unix pa
> And that sys_error message is, I believe, the exact error I am seeing.
> What I am wondering is how did I manage to invoke this by using ^C? Did
> I hit some small window when readline was not running and when the
> program that would normally catch the kill signal was not listening
> (i.e. bash
Serge Dussud wrote:
>
> Hi Chet,
>
> any follow-up on this ?
Haven't looked at it yet, sorry.
Chet
--
``The lyf so short, the craft so long to lerne.'' - Chaucer
Chet Ramey, ITS, CWRU[EMAIL PROTECTED]http://cnswww.cns.cwru.edu/~chet/
Hi Chet,
any follow-up on this ?
tia,
Serge
[..]
From man page ld(1) (snv_99 box):
-B direct | nodirect
These options govern direct binding. -B direct estab-
lishes direct binding information by recording the rela-
tionship between each symbol refer
Chet,
Thanks for that info.
Due to the circumstances, recompiling bash isn't really an option for me, so
I decided to deal with it by having ssh invoke a script that could guarantee
~/.bashrc was sourced.
Regards,
jon seymour.
On Wed, Oct 15, 2008 at 1:24 PM, Chet Ramey <[EMAIL PROTECTED]> wro
There is code in "execute_cmd.c" function "execute_command_internal":
...
#if defined (RECYCLES_PIDS)
last_made_pid = NO_PID;
#endif
last_pid = last_made_pid;
...
if (already_making_children && pipe_out == NO_PIPE &&
last_made_pid != last_pid)
{
...
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 built-in knowledge of Unix pathnames.
For
I got no answer, so I'll send again.
Hi,
To improve bashdb, a bash debugger, we submitted two patches to bash,
adding readfile builtin and removing bashdb.el ever. I hope you don't
forget it:)
We would like submit one more patch, adding set0 builtin.
The purpose of set0 in the debugger is that
14 matches
Mail list logo
