2013-01-19 02:48:40 +01:00
|
|
|
#+TITLE: baps1
|
|
|
|
#+LINK: src http://code.ryuslash.org/cgit.cgi/baps1/
|
|
|
|
#+LINK: tar_gz http://code.ryuslash.org/cgit.cgi/baps1/snapshot/baps1-master.tar.gz
|
|
|
|
#+LINK: zip http://code.ryuslash.org/cgit.cgi/baps1/snapshot/baps1-master.zip
|
|
|
|
#+LINK: readme http://code.ryuslash.org/cgit.cgi/baps1/about/
|
|
|
|
#+LINK: manual http://ryuslash.org/projects/baps1/manual/
|
|
|
|
#+STARTUP: showall
|
|
|
|
|
|
|
|
#+begin_html
|
|
|
|
<script src="/keyjs.js" type="text/javascript"></script>
|
|
|
|
<script type="text/javascript">
|
|
|
|
keyjs_initialize({ "u": [ "keyjs_goto", "../index.html" ],
|
|
|
|
"h": [ "keyjs_goto", "http://ryuslash.org" ] });
|
|
|
|
</script>
|
|
|
|
#+end_html
|
|
|
|
|
|
|
|
#+INCLUDE: "dlmenu.inc"
|
|
|
|
|
|
|
|
* What does it do?
|
|
|
|
|
|
|
|
baps1 offers a, hopefully, efficient and easy way to add certain
|
|
|
|
data to your PS1 (prompt).
|
|
|
|
|
|
|
|
* Why was it written?
|
|
|
|
|
|
|
|
A friend of mine wanted a better way to get some functionality into
|
|
|
|
his PS1 that he was using a PHP script for, I knew how to do that
|
|
|
|
in C and thought it would be a fun project and good learning
|
|
|
|
experience, so here we are.
|
|
|
|
|
|
|
|
* Who is it for?
|
|
|
|
|
|
|
|
Anyone who likes to have the data this project provides in their
|
|
|
|
PS1.
|
|
|
|
|
|
|
|
* Data
|
|
|
|
|
|
|
|
| Version | 0 (development only) |
|
|
|
|
| Language | C |
|
2013-01-19 02:59:16 +01:00
|
|
|
| License | GPLv3 |
|
2013-01-19 02:48:40 +01:00
|
|
|
|
|
|
|
** Features
|
|
|
|
|
|
|
|
- Show the PTY or TTY you are using.
|
|
|
|
- How long ago the last call to baps1 was on that terminal, which
|
|
|
|
should also indicate how long ago your PS1 was printed last.
|
|
|
|
|
|
|
|
** Dependencies
|
|
|
|
|
|
|
|
Apart from the usual build tools (make, gcc) I know of none,
|
|
|
|
though I do have a preference for GNU programs/libraries, so there
|
|
|
|
might be some GNU-only code in there.
|
|
|
|
|
|
|
|
* More...
|
|
|
|
|
|
|
|
For further instructions I would refer you to the [[readme][README]] and [[manual][manual]].
|