Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

a few suggestions/issues #18

Closed
rbenson opened this issue Jun 14, 2017 · 11 comments
Closed

a few suggestions/issues #18

rbenson opened this issue Jun 14, 2017 · 11 comments
Assignees
Milestone

Comments

@rbenson
Copy link

rbenson commented Jun 14, 2017

  • 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
Copy link
Owner

pajoma commented Jun 22, 2017

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. Show recent notes  #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.

@pajoma pajoma self-assigned this Jun 22, 2017
@pajoma pajoma added this to the 0.6.0 milestone Jun 22, 2017
@rbenson
Copy link
Author

rbenson commented Jun 25, 2017

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
Copy link
Owner

pajoma commented Jun 26, 2017

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

  1. 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
Copy link
Author

rbenson commented Jun 27, 2017

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

@pajoma
Copy link
Owner

pajoma commented Jun 28, 2017

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

@rbenson
Copy link
Author

rbenson commented Jun 29, 2017

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

@pajoma pajoma modified the milestones: 0.6.0, 0.8.0 Oct 9, 2017
@flyisland
Copy link

I'd like to try a calendar widget

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

@pajoma
Copy link
Owner

pajoma commented Dec 21, 2017

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
Copy link
Owner

pajoma commented Jun 3, 2018

Regarding the widget: please checkout this extension

@pajoma
Copy link
Owner

pajoma commented Jun 3, 2018

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

@pajoma
Copy link
Owner

pajoma commented Sep 23, 2018

All suggestions are implemented in new version.

@pajoma pajoma closed this as completed Sep 23, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants