I am still just looking at the source code....Trying to figure out how it works.
Regards, Pranav On Mon, May 22, 2017 at 4:30 PM, Pierre Gaston <pierre.gas...@gmail.com> wrote: > I'd suggest that you look into the loadable builtin examples in the > tarball and find ideas to write a couple of these. > > For instance, you could try to write a Json parser that allows callback > and set some bash variables mirroring the Json in an associative array or > something like that. > > There is little documentation so as a result you kind have to look around > in bash source code, and cool builtins could be a way to contribute to bash. > > At least that's what I do ( https://github.com/pgas ), even though I have > no real ambition doing this :D > > Pierre > > On Mon, May 22, 2017 at 1:27 PM, Pranav Deshpande < > deshpande.v.pra...@gmail.com> wrote: > >> Thank you. >> It seems that there is no read to implement this feature. Could you >> suggest >> me some bug so that I can get started? >> Something which is simple for a beginner? >> >> Regards, >> Pranav. >> >> On Mon, May 22, 2017 at 3:06 AM, Eduardo Bustamante <dual...@gmail.com> >> wrote: >> >> > On Sun, May 21, 2017 at 11:29 AM, Pranav Deshpande >> > <deshpande.v.pra...@gmail.com> wrote: >> > > The lssue here: https://savannah.gnu.org/support/?109000 interests >> me. >> > > It's something that I have experienced while using the shell. I am >> > > interested in solving it >> > >> > That bug report lacks detail. There are already ways of sharing >> > history between multiple sessions. Some of the alternatives are >> > outlined here: https://unix.stackexchange.com/questions/1288/preserve- >> > bash-history-in-multiple-terminal-windows >> > >> > Give these a try first. >> > >> > > Any ideas so as how can I get started with the code base? >> > >> > If you're interested in the implementation, review: >> > >> > dualbus@debian:~/src/gnu/bash$ head -n1 bashhist.c builtins/history.def >> > ==> bashhist.c <== >> > /* bashhist.c -- bash interface to the GNU history library. */ >> > >> > ==> builtins/history.def <== >> > This file is history.def, from which is created history.c. >> > >> > And if you want to go into even more detail, review the history >> > library as implemented by GNU readline (and bundled with bash): >> > >> > dualbus@debian:~/src/gnu/bash$ head -n1 lib/readline/hist*c >> > ==> lib/readline/histexpand.c <== >> > /* histexpand.c -- history expansion. */ >> > >> > ==> lib/readline/histfile.c <== >> > /* histfile.c - functions to manipulate the history file. */ >> > >> > ==> lib/readline/history.c <== >> > /* history.c -- standalone history library */ >> > >> > ==> lib/readline/histsearch.c <== >> > /* histsearch.c -- searching the history list. */ >> > >> > >
