Something you could discuss is the expectations that BeOrg has in the format of the Org files (if any).
Blank lines -- I put in blank lines for readability. Will BeOrg remove them and where? Be precise.
Auto-fill -- Should we fill paragraphs or let it wrap at the end of a line? I'm an old Emacs user, so I tend to turn on auto-fill.
CRLF vs NL -- How does BeOrg hand EOL? If I mostly edit on a PC (CRLF), will that cause problems with BeOrg?
How is BeOrg on other character sets?
3 months ago
Regarding blank lines beorg currently:
Removes any blank lines before a heading (this includes at the start of a file)
Keeps any blank lines after a heading
Keeps any blank lines in notes following a heading, except those before the next heading (this is the same as lines before a heading)
Auto fill adds newlines to fill the paragraph to the desired line width or screen width in Emacs. This can result in beorg showing your notes with a staircase-ish effect at the end of the lines and will make large edits more difficult. I personally use soft wrapping in Emacs, i.e. visual-line-mode. The soft wrapping that then happens in beorg when editing text the matches the behaviour of that in Emacs and makes larger edits easier. (http://ergoemacs.org/emacs/emacs_long_line_wrap.html). However like with many things Emacs this is very much a personal preference :)
CRLF vs NL:
beorg will read files saved with CRLF line endings without any issue. If the lines which have those endings are not modified then the CRLF line endings are retained. However any new lines added will just have LF line endings.
In my testing of this before editing the file in beorg the 'file' command in macOS told me ASCII text, with CRLF line terminators, after beorg had inserted some new lines in the file the 'file' command then reported ASCII text, with CRLF, LF line terminators to indicate both types of newline. Using hexdump to look at the file I can see this is the case.
So you shouldn't have any problems but do expect beorg to use just LF line terminators for any new lines added to the files.
Other character sets:
beorg will only read files if it can intepret them with a utf-8 encoding. Files are always written in utf-8.
I do have a possible future feature down so that users can configure beorg to accept and write with other encodings - however I think only one user has requested this so far.
If you see anything in your beorg usage which contradicts the above please let me know and I'll investigate.
Great question, should be very useful for other users - thanks David!