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
timedot: add payee/description and trailing comment/tags #1754
Comments
Closed in favour of #1220 #1220 (comment) |
Related to #1220 (comments in timeclock format). Let's keep this one open for timedot specifically. |
Following up on djp's timedot comment there:
|
I'm confused. "timedot supports descriptions".. how? I get an error putting anything after the date. I often put a comment like copying mockup back to the correct topic UPDATE; oh what the hell. I've been thinking about a more complete feature set, and considering eeking them out, as the foundational bits get deployed, so as not to cause alarm, but I'm expanding this mockup with status "*" and (number).
|
Eg:
|
(It works for me at least back to hledger 1.17..) |
Oh that's cool on the date (emacsism?) but I'm after a description on the entry
|
Yes, in that position I propose we should support comments ( |
Well.. I'm getting confused, I thought the date creates a transaction and each dot line is a posting within it. Actually, each dot line is a separate transaction. (Is that for the best ? I'm not sure.) |
yes, it's (nearly) perfect! |
timedot entries being a one-liner, with an inherited date, is my favorite part of it, but it only has a date, an account and an amount, no description (or comment or tag). I suspect that some of the timedot behaviors you are seeing (Simon) is emacs magic, and none of the leading-* features described work in my editor (vi) and that's ok (for now) . Have another look at the mockup above, and I hope you'll agree that it might be the most concise, most hledgerish way to cram the full data set into a single line. |
@linuxcaffe and I, the current known users of timedot format, discussed this (cf today's #hledger chat log) and made some decisions. We'd like to get better description and comment support in timedot format, along these lines:
If all of those are implemented, the above would produce transactions like these, queryable in the usual ways:
|
@simonmichael and/or @linuxcaffe - do either of you know of anyone working this issue at this time? I am a daily user of the timedot format and would like to implement this, as I have wished for the same thing! |
Noone is working on it, be our guest @alhirzel . |
Here's a RFC on changes to timedot format: https://groups.google.com/g/hledger/c/TxoA-xnfvMA/m/QvpmWA5pAwAJ |
Ccing here (and reviewing the discussion above): I'm fixing/improving timedot's description/comment/tag parsing. But before that..
->
Or 2. generating one big transaction per date line ?
I don't remember why it's implemented as 1. Right now, 2 looks a little tidier ? The above affects how timedot format can support descriptions and comments (and tags). |
Descriptions and comments are now more straightforward and similar to journal format.
Descriptions and comments are now more straightforward and similar to journal format.
Now implemented in master: https://hledger.org/dev/hledger.html#timedot |
The most awesome timedot would be even awesomer with a description (payee field).
Currently a timedot entry carries no description, but can handle a trailing comment.
<acct:sub:sub><spaces><qtty><spaces><;><comment>
This enhancement would use the comment as description.
The text was updated successfully, but these errors were encountered: