jaredk3nt/hometerm

A "functioning" terminal as your browsers homepage!

hometerm's Issues

Tab autocomplete

To properly match the user-experience of a terminal HomeTerm should provide tab autocomplete. Set up a listener on tabs that will fill input based on current string.

For the first run we don't need to support tabbing through options just displaying multiple options if available and completing if only a single option is available.

`edit` command

HomeTerm should expose an edit command that allows users to update the url values attached to links.

usage: edit <path to link> <new value>

Ability to change search engine

The user should be able to change their default search engine permanently or for one time on the command. They should also be able to set their search engine to something custom.

usage: search -e <engine name or url string> [<search string>]

examples:
search -e duckduckgo - changes engine to duckduckgo and remembers change in localstorage
search -e duckduckgo "search string" - changes engine to duckduckgo for the one search
search -e https://anothersearch.com/q= - changes engine to use custom string

engines to add default:
duckduckgo: https://duckduckgo.com/?q=
bing: https://www.bing.com/search?q=

Neofetch and other silly commands

Just adding a neofetch command that displays some fake system information like the neofetch command on linux, or a cowsay command, just some more silly things

`mv` command

HomeTerm should expose a mv command for renaming directories and links.

usage: mv <path> <new name>

Add "config" for terminal

Add a separate mechanism for configuration.

Options: (These don't have to all be added at once)

• Prompt styling / format
• Option to run command at load
• Size of terminal
• Size of font

`import` and `export`

HomeTerm should expose commands to allow for importing and exporting file structures. The file structure should be serialized to allow for easier copy/past.

usage: import <serialized object> and export