a few suggestions/issues

pajoma / vscode-journal

Lightweight journal and simple notes support for Visual Studio Code

https://marketplace.visualstudio.com/items?itemName=pajoma.vscode-journal

GNU General Public License v3.0

233 stars 40 forks source link

a few suggestions/issues #18

Closed rbenson closed 5 years ago

rbenson commented 7 years ago

Have you thought about maybe flattening the structure? As is I see this being useful if you need to do daily break downs, or bullet journal type stuff, but if you don't need that level of detail, it is hard to use. I am seeking an orgmode replacement. If I know I made a note somewhere, how can I easily get to it?
have you thought about adding in your own language syntax? this would be useful if you want to give task/MEMO unique looks
I get "Journal input not recognized" when making a memo, even the sample you have in the readme

pajoma commented 7 years ago

Hi, good questions:

1) I am not sure I've fully understand the "flattening" part. Could you give an example of an higher level of detail (e.g. define a task on a week level should be doable)

2) "Browsing to the notes" is on my todo list. #8 tracks this issue. Next release should include the new view in sidebar feature, which came in the latest vscode version. I'd like to try a calendar widget, with pages having notes or todos being marked as such.

3) Can you maybe give an example, which is not yet covered by the settings? (I know, I should probably document this better)

4) I'll look into it. Happens sometimes to me as well, will be covered in the next release.

rbenson commented 7 years ago

Hi there,

1- Most of my projects span anywhere from a few weeks to almost a year, and a fair amount of they don't have daily activities. If I open today's log, note something, it may be impossible to find in 1+ weeks. I guess I could keep a master file and link everything afterwards, but putting everything in a master would be easier.

is your third item in your list in regards to my syntax suggestion?

pajoma commented 7 years ago

Opened a new issue #19 regading the "flattening" for projects.

3) Yes, I am note what you mean about the unique looks.

I used asciidoc when I started this project and switched to markdown. The extension is synax-independent, format and structure is defined in the settings (with default using markdown). My tasks list looks like this

*Tasks*
- [ ] TODO: Something to think about
- [x] TODO: Another thing I thought about

The settings for this are

"journal.tpl-page": "# {content}\n\n*Tasks*\n",
"journal.tpl-task": "- [ ] TODO: {content}", 
"journal.tpl-task-after": "*Tasks*",

rbenson commented 7 years ago

I was thinking about giving keywords special looks, like TODO: bold and red.

pajoma commented 7 years ago

Ah, you are thinking about syntax highlighting. Yes, should be doable, I will look into it.

rbenson commented 7 years ago

I am gueessing ext can extend a language vs having to override it

flyisland commented 6 years ago

I'd like to try a calendar widget

@pajoma, I'm looking forward to this widget, when'll it available on vscode-journal?

pajoma commented 6 years ago

The calendar widget is a bit complicated, since the views extension (in the sidebar) only supports tree-like structures. It's on my todo list (but not coming anytime soon).

pajoma commented 6 years ago

Regarding the widget: please checkout this extension

pajoma commented 6 years ago

Syntax highlighting in its first version is now in 0.6.0. Feedback is appreciated.

pajoma commented 5 years ago

All suggestions are implemented in new version.