mirror of
https://github.com/jrnl-org/jrnl.git
synced 2025-06-27 21:16:14 +02:00
New make options
This commit is contained in:
parent
be1a90db3d
commit
5b4e89f081
4 changed files with 17 additions and 10 deletions
8
docs/_themes/jrnl/static/less/docs.less
vendored
8
docs/_themes/jrnl/static/less/docs.less
vendored
|
@ -108,15 +108,11 @@ a:hover, a:active
|
|||
{
|
||||
background:transparent !important;
|
||||
}
|
||||
.highlight-output
|
||||
{
|
||||
.pre-block;
|
||||
background: desaturate(lighten(@terminal,10), 10);
|
||||
}
|
||||
.highlight-javascript
|
||||
.highlight-output, .highlight-javascript, .highlight-sh
|
||||
{
|
||||
.pre-block;
|
||||
background: desaturate(lighten(@terminal,10), 10);
|
||||
pre {color: white;}
|
||||
}
|
||||
.highlight-python
|
||||
{
|
||||
|
|
|
@ -44,7 +44,9 @@ If you want to import a file as an entry to jrnl, you can just do ``jrnl < entry
|
|||
|
||||
echo `stat -f %Sm -t '%d %b %Y at %H:%M: ' entry.txt` `cat entry.txt` | jrnl
|
||||
|
||||
The first part will format the modification date of ``entry.txt``, and then combine it with the contents of the file before piping it to jrnl. If you do that often, consider creating a function in your ``.bashrc`` or ``.bash_profile`` ::
|
||||
The first part will format the modification date of ``entry.txt``, and then combine it with the contents of the file before piping it to jrnl. If you do that often, consider creating a function in your ``.bashrc`` or ``.bash_profile``
|
||||
|
||||
.. code-block:: sh
|
||||
|
||||
jrnlimport () {
|
||||
echo `stat -f %Sm -t '%d %b %Y at %H:%M: ' $1` `cat $1` | jrnl
|
||||
|
@ -57,9 +59,11 @@ Using templates
|
|||
Say you always want to use the same template for creating new entries. If you have an :doc:`external editor <advanced>` set up, you can use this ::
|
||||
|
||||
jrnl < my_template.txt
|
||||
jrnl -1 --edit
|
||||
$ jrnl -1 --edit
|
||||
|
||||
Another nice solution that allows you to define individual prompts comes from `Jacobo de Vera <https://github.com/maebert/jrnl/issues/194#issuecomment-47402869>`_ ::
|
||||
Another nice solution that allows you to define individual prompts comes from `Jacobo de Vera <https://github.com/maebert/jrnl/issues/194#issuecomment-47402869>`_:
|
||||
|
||||
.. code-block:: sh
|
||||
|
||||
function log_question()
|
||||
{
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue