Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] Shell history w/ ASH spans multiple ash instances
Date: Thu, 19 Feb 2009 16:14:56 +0100	[thread overview]
Message-ID: <877i3ma26n.fsf@macbook.be.48ers.dk> (raw)
In-Reply-To: <499D717F.9010003@bvwireless.net> (Eric Malkowski's message of "Thu\, 19 Feb 2009 09\:49\:35 -0500")

>>>>> "Eric" == Eric Malkowski <eric@bvwireless.net> writes:

Hi,

 Eric> To follow up briefly: In looking at the source in libbb it appears
 Eric> disabling CONFIG_FEATURE_EDITING_SAVEHISTORY will stop libbb from
 Eric> writing to ~/.ash_history
 Eric> Older versions I've used had SAVEHISTORY enabled but didn't
 Eric> dynamically load it from various instances of interactive shells
 Eric> causing thr cross-shell history sharing -- perhaps this is a new
 Eric> "feature".  I don't need the history saved and loaded constantly or on
 Eric> shell exit so I'll try turning that off.

Ok.

 Eric> Sorry for using the wrong list -- but at least you can see my
 Eric> reasoning for starting w/ the buildroot list.

No problem, it's just that (even though there's a certain overlap
between buildroot and busybox people) the busybox people normally know
the finer details of their program better than we do.

 Eric> If anything further is needed w/ this topic, I'll move over to the
 Eric> busybox list.

Thanks.

-- 
Bye, Peter Korsgaard

      reply	other threads:[~2009-02-19 15:14 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-19  5:12 [Buildroot] Shell history w/ ASH spans multiple ash instances Eric Malkowski
2009-02-19  9:58 ` Peter Korsgaard
2009-02-19 14:49   ` Eric Malkowski
2009-02-19 15:14     ` Peter Korsgaard [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=877i3ma26n.fsf@macbook.be.48ers.dk \
    --to=jacmet@uclibc.org \
    --cc=buildroot@busybox.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox