You wrote:
> Junio C Hamano wrote:
> >
> > How greppable and "log -p"-able is the documentation written in LyX?
>
> LyX format is plain text, loosely based on LateX. Here's attached a
> sample .lyx file FYI. We have one tag per line and a maximum of 80 char
> per line so that the format is easily parsable. Advanced users often use
> unix tools (grep, sed, etc) to modify the .lyx file manually.
Is it just me or is the format very hard to read? For example, line
492ff spells a list of quoted items as
\begin_layout Standard
Generally, you would send email to lyx-foo-subscribe@xxxxxxxxxxxxx to subscribe
to these lists or to lyx-foo-unsubscribe@xxxxxxxxxxxxx to unsubscribe, where
\begin_inset Quotes eld
\end_inset
foo
\begin_inset Quotes erd
\end_inset
is one of
\begin_inset Quotes eld
\end_inset
announce
\begin_inset Quotes erd
\end_inset
etc. Of course I can "parse" the language, but my untrained eye is
unable to fluently read the text hiding behind it.
Also, if I made a commit changing the "announce", you would have to
turn up diff context to at least 13 lines to get any _semantic_
context of the change.
- Thomas
Attachment:
signature.asc
Description: This is a digitally signed message part.
