phonetonote / phonetonote-logseq Goto Github PK

make the block messages are outputted to configurable and/or allow messages to be appended to Journals

if a parent block for a given day exists from a previous sync, new messages should go under that, instead of making a new one

when we parse dates around semicolons, such as ;next friday;, they should parse into the user's date format. we do the parsing on the ptn backend, so this might need to be a separate ptn preference, which isn't quite ideal but not that big of a deal. moving the parsing to client side would make the feed data more complex.

this is not yet reading attachments, which breaks images, audio messages and link enrichment

Using "open settings" from the LogSeq plugin page opened two text files but unfortunately I closed them and now it doesn't open them again.

See https://discord.com/channels/725182569297215569/896368413243494430/920406779484045393

Hey, small request:

Today, to fetch the things I've captured on Phonetonote, I need to manual press:

Is it possible to have a setting to set an automatic pull (every 30 sec/ 1min/ 2min/ 5min/ 15min/ 60min) to pull things into Logseq? That's how it is in Roam Research, but not in Logseq.

(I constantly forget to manually press it, when processing my inbox)

allow a settable hashtag to append to each message coming

Ah. Ok, I didn't notice that icon.

I clicked it, and briefly get make a block called ptn_key on this page and put your ptn_key under it but then the message disappears, just FYI

yea, towards the very top of my dev todo list is making the ui/ux better here, I just used the default logseq error message as a quick mvp

Originally posted by @scottrblock in #5 (comment)

Hi,

Would it be possible to add new PTN messages to the bottom of the journal page instead of to the top when you leave the parent block empty?

By the way Incredible service. I really appreciate it :-)

When capturing via Email, the behaviour is different between Roam vs Logseq.

In Roam:

1. The email is captured, by forwarding to [email protected]
2. As a parent block, we get the title of the email
3. As a child block, we get the body of the email

In Logseq:

1. The email is captured, by forwarding to [email protected]
2. As a parent block, we get the title of the email
3. No child block

This doesn't seem like the intended behavior (when looking at the code, is seems like there's a part that is supposed to add children blocks (line 107-108).

multiple day's notes end up nested incorrectly:

this is likely just a small tweak to how the block needs to be inserted