Major chhanges: daisy.source renamed to ld.source.
All files have been prettified by making sure we use 2-space indent. agenda: Instead of the hidden .tree file, a file created "More..." is made. You can use (ex) "agenda --view "2026" to get a full list of files from that year/date/day. Additionally, minor fixes have been made. clip: You can now use "-c" to clear the clipbaord.
This commit is contained in:
parent
056ab01ed4
commit
ab730db2f7
14 changed files with 264 additions and 534 deletions
83
README.md
Executable file → Normal file
83
README.md
Executable file → Normal file
|
|
@ -1,19 +1,31 @@
|
|||
---*This project is still under heavy development!*---
|
||||
Please do not delete this file, as it is used to display help information.
|
||||
|
||||
# L A C K A D A I S I C A L
|
||||
A collection of easy-to-understand, easy-to-use scripts, functions and aliases. Designed to be beginner-friendly but also useful!
|
||||
A collection of easy-to-understand, easy-to-use scripts, functions and aliases.
|
||||
Designed to be beginner-friendly but also useful! Contains several tools you 0ccould
|
||||
|
||||
## Disclaimer
|
||||
Some aspects of this project were generated by Google Gemini (in particular, daisy_help and daisy_liist). While we are generally against using LLMs for code, the added functionality of being able to get information for individual tools is useful and not considered to be vital functionality.
|
||||
Some aspects of this project were generated by Google Gemini (in particular,
|
||||
daisy_help and daisy_liist). While we are generally against using LLMs for
|
||||
code, the added functionality of being able to easily update information for
|
||||
individual tools is useful and not considered to be vital functionality.
|
||||
|
||||
## How to use
|
||||
Simply open your shell's RC-file (.bashrc, .zshrc, etc) and include `source <la
|
||||
ckadaisical-folder>/daisy.source`, preferably at the bottom of the file. We recommend setting your editor before sourcing `lackadaisical`. For instance, putting `export EDITOR=/usr/bin/nano` near the top of your RC-file. It may later be overridden by `lackadaisical` itself if you use (or have used) `ched`.
|
||||
Simply open your shell's RC-file (.bashrc, .zshrc, etc) and include
|
||||
`source <lackadaisical-folder>/ld.source`, preferably at the bottom of the file.
|
||||
We recommend setting your editor before sourcing `lackadaisical`. For instance,
|
||||
putting `export EDITOR=/usr/bin/nano` near the top of your RC-file. It may
|
||||
later be overridden by `lackadaisical` itself if you use (or have used) `ched`.
|
||||
|
||||
You can also try out the utilities by simply sourcing the file while running your shell of choice. It will automatically include itself into your `PATH` variable.
|
||||
You can also try out the utilities by simply sourcing the file while running
|
||||
your shell of choice. It will automatically include itself into your `PATH`
|
||||
variable.
|
||||
|
||||
At first use, `lackadaisical` will provide you with information via `daisy_help`. This information is identical to what can be read in the `Getting Started` section below.
|
||||
At first use, `lackadaisical` will provide you with some information. This
|
||||
information is identical to what can be read in the `Getting Started` section
|
||||
below.
|
||||
|
||||
Please use `daisy help` to see this message again if you get lost!
|
||||
|
||||
## Getting started
|
||||
```
|
||||
|
|
@ -30,6 +42,10 @@ specifying an env value of; NO_ARCHIVEMOUNT=1. The standard script supports
|
|||
zip, tarballs, and rar archives. We recommend relying on archivemount` if you
|
||||
have it installed. Use "--check" to only check if a file is an archive. It
|
||||
returns 0 if it is, 1 otherwise.
|
||||
|
||||
Usage: cdz <archive>
|
||||
cdz --check <archive>
|
||||
Returns: (with --check) 0 if file is archive, 1 if it is not.
|
||||
················································································
|
||||
|
||||
< squasher >
|
||||
|
|
@ -58,6 +74,9 @@ take the same folder argument:
|
|||
Uses your standard CLI editor to create/modify a file and make it executable.
|
||||
If the executable already exists in path, it will edit that instead.
|
||||
Should you not want this behavior, call the utility with the -n switch.
|
||||
|
||||
Usage: editx <file_local_or_in_path>
|
||||
editx -n <file>
|
||||
················································································
|
||||
|
||||
< filewait >
|
||||
|
|
@ -66,6 +85,9 @@ This tool is given a filename of a file that does not exist yet. When the file
|
|||
appears on disk, the tool quits and simply returns the filename. This can be
|
||||
used in personal workflows to stall a longer command that relies on the
|
||||
existence of said file.
|
||||
|
||||
Usage: filewait <inexistant_file>
|
||||
Returns: filename specified as argument
|
||||
················································································
|
||||
|
||||
< agenda >
|
||||
|
|
@ -78,6 +100,21 @@ automatically cleans up empty folders. A symbolic link to the base of the
|
|||
folder's tree, ".tree", is created in the root of the specified directly. Can
|
||||
be used for everything you'd like to sort by date. For example; a diary,
|
||||
browser downloads, backups, code.
|
||||
|
||||
There is a switch available:
|
||||
--view <date>: Lists all entries recursively. For example, if used with a year
|
||||
like "agenda --view "2026" <folder>", you will get a full
|
||||
directory listing of all entries in 2026 recursively.
|
||||
If you specify a month as well, you get all the entries from
|
||||
said month. You can also select a specific date, but it it does
|
||||
not exist, you will not get any results. Additionally, you need
|
||||
to use the date structure YYYY/MM/DD.
|
||||
Each day will be listed with a full path, allowing you to cd to
|
||||
them (hint: The ".tree" symlink in your folder also allows you
|
||||
to browse the tree).
|
||||
|
||||
Usage: agenda <folder>
|
||||
agenda --view <folder>
|
||||
················································································
|
||||
|
||||
< own >
|
||||
|
|
@ -92,8 +129,12 @@ This is a wrapper for `ssh`, the meaning of the 'p' is "Plus". Integrates SSHFS
|
|||
support. If both client and host have SSHFS, this wrapper can be used to
|
||||
connect their file systems. For example, if you need to move files from one
|
||||
machine to another, you could do something like this: "sshp -m /:/mnt/pc -m
|
||||
/home/claire:/home/claire claire@pyon.net" If privilege escalation is necessary
|
||||
for FS access, you will be asked for a password.
|
||||
/home/claire:/home/claire claire@pyon.net". Each "-m" switch indicates a
|
||||
Docker-style mapping from a local directory to a remote directory.
|
||||
If privilege escalation is necessary for FS access, you will be asked for a
|
||||
password.
|
||||
|
||||
Usage: sshp -m <local>:<remote> [user@]host [ssh_options]
|
||||
················································································
|
||||
|
||||
< shrc >
|
||||
|
|
@ -114,10 +155,15 @@ returns partial matches. It can be used to search for binaries.
|
|||
················································································
|
||||
|
||||
< scriptbox >
|
||||
················································································
|
||||
························································q························
|
||||
This tool can be used to pack bash scripts into one big megascript, much like
|
||||
how `busybox` works. You can also make symlinks to it to invoke a specific
|
||||
script.
|
||||
script. Standard binaries are not supported.
|
||||
|
||||
Usage:
|
||||
Creating boxed binary: scriptbox -o <BOXED_BIN> <-s source files>
|
||||
<-p include files verbatim> -i INPUT_BINS ...
|
||||
More information: scriptbox <no-args>
|
||||
················································································
|
||||
|
||||
< bak/unbak >
|
||||
|
|
@ -174,19 +220,24 @@ Similar to `cdf` but uses tree+peco for the query.
|
|||
An extremely simple utility that functions as a clipboard of sorts. To set the
|
||||
variable, run "clip <data>" or provide data via stdin. To get the variable,
|
||||
simply run clip without any arguments. The variable is stored locally in the
|
||||
shell as "LD_CLIP".
|
||||
shell as "LD_CLIP". Run with switch "-c" to clear LD_CLIP.
|
||||
|
||||
Usage: clip <anystring>
|
||||
clip -c
|
||||
clip
|
||||
Returns: Without arguments, the contents of LD_CLIP.
|
||||
················································································
|
||||
|
||||
< ldrc >
|
||||
················································································
|
||||
Edits daisy.source and re-sources it, similarly to shrc. Append "-e" to edit
|
||||
Edits ld.source and re-sources it, similarly to shrc. Append "-e" to edit
|
||||
"extra.src", to add custom functions in the lackadaisical namespace.
|
||||
Append "-d" to edit "daisy.command.source".
|
||||
················································································
|
||||
|
||||
< daisy reload >
|
||||
················································································
|
||||
Re-sources daisy.source. Essentially `ldrc` without editing.
|
||||
Re-sources ld.source. Essentially `ldrc` without editing.
|
||||
················································································
|
||||
|
||||
< grab >
|
||||
|
|
@ -288,3 +339,7 @@ functions provided by `lackadaisical`.
|
|||
················································································
|
||||
<!-- --- END OF DAISY HELP --- -->
|
||||
```
|
||||
|
||||
# Future plans
|
||||
We will keep improving and enhancing the scripts. Possibly, we will add new
|
||||
utilities. We hope you found LACKADAISICAL useful.
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue