Support XDG
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 44.7k
- Forks
- 3.6k
- Avg merge
- 21m
- Merged PRs (30d)
- 1
Description
Hi,
I just discovered Hyperterm today and I'm really liking the idea of a web-based terminal (I use Atom as my code editor of choice). However, reading through the documentation, I noticed that configuring the editor (plugins and all) creates several files in your home directory (i.e. ~/.hyperterm.js and ~/.hyperterm_plugins). I also found issues on this repo like #10 and #14 which propose a possible custom stylesheet file (as well as the addition of an Extensions API).
I'd prefer not to clutter my home directory with more hidden files, if possible. Therefore, I feel that all of these files should be consolidated under a single ~/.hyperterm directory, similar to Atom's. It could have the following structure:
.hyperterm/
- plugins/
- ...
- config.js
- styles.css (future)
...and whatever else might be added.
I figure to migrate current users to the new hierarchy, some backwards-compatibility code could be added which does the following:
- Use
.hypertermfor all configuration/plugins if the directory exists - If it does not exist, create a new
.hypertermdirectory and move~/.hyperterm.jsand~/.hyperterm_pluginsto their new respective paths
Thoughts? :)
Caleb
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No implementation files or tests are named in the issue. Locate the code that reads ~/.hyperterm.js and manages ~/.hyperterm_plugins, then trace how configuration and plugins are initialized; done means supporting the ~/.hyperterm hierarchy while preserving migration for existing users.
Written by the indexing model from the issue text.
Assessment
- Domain
- desktop
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100