You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When using jrnl with a text editor, a temporary file is created with the name jrnl12345.txt, where 12345 is a random identifier. Rather than a random filename with a generic file extension, consider one of the two following changes:
A fixed filename such as JRNL_ENTRY (this matches git's behavior in a similar context)
Or, a unique file extension such as .jrnl
If backwards compatibility is a concern, this change could be implemented as an optional config setting.
Use Case/Motivation
Although there is not much syntax in these temporary jrnl entry files, it would still be nice to highlight the title line and tags. Like using a text editor to write commit messages for git, the extra context from syntax highlighting would make the input process clearer and more pleasant.
Unfortunately the current temporary files, with their random names and plain text file extension, are quite difficult to distinguish in many editors. Something either more predictable or with a unique file extension would be much simpler to target with custom editor settings and plugins.
Other information
I am most interested in this change in order to hook into custom syntax highlighting, but I imagine it would be useful for other text editor integrations as well down the road.
The text was updated successfully, but these errors were encountered:
@wren and I talked about this and we like the .jrnl extension as a default. It doesn't seem to be used by any other program we can identify, so it could fit this syntax highlighting concern quite nicely for all sorts of editors.
Issue #1059 is very similar to this also, but I think that issue is more about customization rather than defaults, so I'd like to keep both of these open as separate issues.
Feature Request
When using jrnl with a text editor, a temporary file is created with the name
jrnl12345.txt
, where12345
is a random identifier. Rather than a random filename with a generic file extension, consider one of the two following changes:JRNL_ENTRY
(this matches git's behavior in a similar context).jrnl
If backwards compatibility is a concern, this change could be implemented as an optional config setting.
Use Case/Motivation
Although there is not much syntax in these temporary jrnl entry files, it would still be nice to highlight the title line and tags. Like using a text editor to write commit messages for git, the extra context from syntax highlighting would make the input process clearer and more pleasant.
Unfortunately the current temporary files, with their random names and plain text file extension, are quite difficult to distinguish in many editors. Something either more predictable or with a unique file extension would be much simpler to target with custom editor settings and plugins.
Other information
I am most interested in this change in order to hook into custom syntax highlighting, but I imagine it would be useful for other text editor integrations as well down the road.
The text was updated successfully, but these errors were encountered: