String leterals in Beancount files

28 views
Skip to first unread message

Daniele Nicolodi

unread,
Jun 25, 2020, 11:49:29 AM6/25/20
to Beancount
Hello,

I would like to propose some changes to how string literals (typically
encountered as payee and narration in transactions, values of metadata
entries, option values, and a few other places) are parsed.

https://github.com/beancount/beancount/issues/486

I don't see practical uses of the problematic features I would like to
remove, but maybe there are some I am not thinking about. Would anyone
that uses those features like to comment?

Thank you.

Cheers,
Dan

Martin Michlmayr

unread,
Jun 25, 2020, 8:28:51 PM6/25/20
to bean...@googlegroups.com
* Daniele Nicolodi <dan...@grinta.net> [2020-06-25 09:49]:
> I would like to propose some changes to how string literals (typically
> encountered as payee and narration in transactions, values of metadata
> entries, option values, and a few other places) are parsed.
>
> https://github.com/beancount/beancount/issues/486
>
> I don't see practical uses of the problematic features I would like to
> remove, but maybe there are some I am not thinking about.

I also didn't like this feature. However, multi-lines can be common
for the "plugin" directive. Changing this might break a lot of beancount
files.

--
Martin Michlmayr
https://www.cyrius.com/

Daniele Nicolodi

unread,
Jun 25, 2020, 10:47:02 PM6/25/20
to bean...@googlegroups.com
I realized that multi line strings are far more common that what I
though. Changing this aspect of the parser is not on the table anymore.
Only the accepted escape sequences will be modified (maybe).

Cheers,
Dan
Reply all
Reply to author
Forward
0 new messages