search

benjypng / logseq-datenlp-plugin

MIT License
73 stars 5 forks source link

Generated date is in wrong format #20

Closed croogie closed 1 year ago

croogie commented 2 years ago

I have a config in form: image but inline dates are generated as image image

am I doing something wrong?

benjypng commented 2 years ago

Please try again in v3.11.2.

cesar-programs commented 2 years ago

I am also experiencing this.

I find the bug occurs when using '@' to parse the date; however, when parsing for a schedule or deadline with % and ^, the plugin works as expected

Automatic parsing also doesn't take into account format in plugin settings

benjypng commented 2 years ago

Are you on the latest version?

cesar-programs commented 2 years ago

UPDATE: tested it today and it works just as expected—coffee bought :)

jacklaing commented 1 year ago

This is happening to me in v3.11.2 for the date format EEE MMM do, yyyy when I do semi-auto parsing with @. I get [[Oct 7th, 2022]] instead of [[Fri Oct 7th, 2022]].

benjypng commented 1 year ago

I don't seem to have "EEE MMM do, yyyy" as an option in Logseq though.

natrius commented 1 year ago

It does not seem to work for me as well. I set E, dd.MM.yyyy and/or EEE, dd.MM.yyyy. Using tomorrow/parse inline results in [[T, 11.10.2022]]. Problem, my sites are labeled Mon, 10.10.2022 -> i tried reindexing after setting from E to EEE, but that did not change anything.

benjypng commented 1 year ago

It does not seem to work for me as well. I set E, dd.MM.yyyy and/or EEE, dd.MM.yyyy. Using tomorrow/parse inline results in [[T, 11.10.2022]]. Problem, my sites are labeled Mon, 10.10.2022 -> i tried reindexing after setting from E to EEE, but that did not change anything.

E => T, while EEE => Tuesday. If you are changing date formats with this plugin, suggest to change date format, then reload the plugin.

natrius commented 1 year ago

But, that does not change the initial problem, doesn't it? I tried with E, dd.MM.yyyy, expected Mon, 10.10.2022 and got [[T, 11.10.2022]]. The change happened afterwards to try around, sorry for the confusion.

jacklaing commented 1 year ago

I don't seem to have "EEE MMM do, yyyy" as an option in Logseq though.

I used the config.edn to apply the date format.

I've tried uninstalling and reinstalling the plugin and I have the same issue.

jacklaing commented 1 year ago

E => T, while EEE => Tuesday

In my experience EEE = Tue, not Tuesday.

benjypng commented 1 year ago

I don't seem to have "EEE MMM do, yyyy" as an option in Logseq though.

I used the config.edn to apply the date format.

I've tried uninstalling and reinstalling the plugin and I have the same issue.

I've only provided support for date formats in the dropdown list. This is perhaps why it isn't working.

Regarding the issue with E and EEE, what I was trying to say is that while E is supposed to be T, Logseq interprets it as an EEE. Hence, it's more foolproof if one avoids using any date formats with just a singular E in it.