I don't see what the point of this is. Every single command can be mapped to an existing Unix tool.
I wrote about that in the FAQ: https://github.com/posce/posce#why-use-this-instead-of-lsgre... ## Why use this instead of ls/grep/wget/etc? Posce is one app using one system on one directory. It's a very focused app, and that focus gives it a level of stability and uniformity I enjoy. Also, by using a single notes directory, you can use disambiguated names and get incredible brevity when entering commands.
Show HN: Posce, a note-taking toolkit for your command-line
21–30 of 32 posts
Re: Show HN: Posce, a note-taking toolkit for your command-line
#22The last thing you or I need is another configuration file clogging up our home directories. This is why the XDG spec exists. Use XDG_CONFIG_HOME, not HOME. I don't feel strongly about config file vs env var for just 2 settings, but seems worth noting. Dropping a dotfile right into your home directory is old school and needs to go away.
To me filling HOME with dotfiles doesn't feel much tidier than filling XDG_CONFIG_HOME with stuff, but I'll take everyone's word for it (even though most people can't seem to explain why they prefer it, can you?).
Would you still feel like dropping things in HOME was tidy if hidden files weren't a thing? You can also back up XDG_CONFIG_HOME without grabbing garbage like cache data.
Re: Show HN: Posce, a note-taking toolkit for your command-line
#23Earlier quoted context omitted.
To me filling HOME with dotfiles doesn't feel much tidier than filling XDG_CONFIG_HOME with stuff, but I'll take everyone's word for it (even though most people can't seem to explain why they prefer it, can you?).
I'm assuming that you accidentally got that statement backwards, because otherwise it doesn't make sense to me. Would you still feel like dropping things in HOME was tidy if hidden files weren't a thing? You can also back up XDG_CONFIG_HOME without grabbing garbage like cache data.
I don't look at my HOME directory often, I usually start from a subdirectory of HOME that has what I'm looking for. Is that why people prefer XDG_CONFIG_HOME, because they look at HOME a lot? I guess I can understand that.
Re: Show HN: Posce, a note-taking toolkit for your command-line
#24I don't agree with the assumptions baked into the tool (eg env vars over config, new vs edit, no deletion), yet I like it being opinionated. Keep coding :)
Re: Show HN: Posce, a note-taking toolkit for your command-line
#25The last thing you or I need is another configuration file clogging up our home directories. This is why the XDG spec exists. Use XDG_CONFIG_HOME, not HOME. I don't feel strongly about config file vs env var for just 2 settings, but seems worth noting. Dropping a dotfile right into your home directory is old school and needs to go away.
I'm a Windows user, which means dotfiles are even uglier for me. For an app that just needs two tiny variables, environs are the much cleaner solution.
Even on my relatively clean Windows system, that directory contains config files generated by NPM and Scoop.
Re: Show HN: Posce, a note-taking toolkit for your command-line
#26Earlier quoted context omitted.
I'm assuming that you accidentally got that statement backwards, because otherwise it doesn't make sense to me. Would you still feel like dropping things in HOME was tidy if hidden files weren't a thing? You can also back up XDG_CONFIG_HOME without grabbing garbage like cache data.
Yes, sorry I got it backwards. I don't look at my HOME directory often, I usually start from a subdirectory of HOME that has what I'm looking for. Is that why people prefer XDG_CONFIG_HOME, because they look at HOME a lot? I guess I can understand that.
Re: Show HN: Posce, a note-taking toolkit for your command-line
#27Earlier quoted context omitted.
To me filling HOME with dotfiles doesn't feel much tidier than filling XDG_CONFIG_HOME with stuff, but I'll take everyone's word for it (even though most people can't seem to explain why they prefer it, can you?).
I'm assuming that you accidentally got that statement backwards, because otherwise it doesn't make sense to me. Would you still feel like dropping things in HOME was tidy if hidden files weren't a thing? You can also back up XDG_CONFIG_HOME without grabbing garbage like cache data.
I actually also prefer putting config files in HOME. I don't feel strongly enough to argue about it, I just prefer it.
Re: Show HN: Posce, a note-taking toolkit for your command-line
#28Earlier quoted context omitted.
I'm assuming that you accidentally got that statement backwards, because otherwise it doesn't make sense to me. Would you still feel like dropping things in HOME was tidy if hidden files weren't a thing? You can also back up XDG_CONFIG_HOME without grabbing garbage like cache data.
"If hidden files didn't exist" doesn't matter because they do exist... I actually also prefer putting config files in HOME. I don't feel strongly enough to argue about it, I just prefer it.
Re: Show HN: Posce, a note-taking toolkit for your command-line
#29Earlier quoted context omitted.
Yes, sorry I got it backwards. I don't look at my HOME directory often, I usually start from a subdirectory of HOME that has what I'm looking for. Is that why people prefer XDG_CONFIG_HOME, because they look at HOME a lot? I guess I can understand that.
Yes, I usually start my shell sessions in $HOME. I also have shell aliases set up so I always see hidden files, and it would drive me crazy if I weren't able to tuck most config files into another directory.
Re: Show HN: Posce, a note-taking toolkit for your command-line
#30I actually want something like this. currently I just use Gnome Evolution for this since it syncs with my corporate EWS automatically. However, one thing I think must be required from such a tool is a full text search engine. The find subcommand appears to only use substrings or regular expressions which can be very limiting when trying to find that note you made about server xyz and some service abc on it. A regex t…