git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: markdown 2 man, was Re: Git Community Book

From
AYAbdelrazak Younes <younes@lyx.org>
Date
Aug 1, 2008, 07:11 UTC
Message-ID
<4892B714.8010401@lyx.org>
In-Reply-To
<7vvdylv9zq.fsf@gitster.siamese.dyndns.org>
Junio C Hamano wrote:
Show 12 quoted lines
> Abdelrazak Younes<younes@lyx.org>  writes:
>
>    
>> I just had a look at the user manual and, well unless you have a
>> special emacs mode or whatever that can automate the markup tag
>> insertion, I wonder how can anybody think that writing with this
>> markup language is easier than within LyX, really (genuine question,
>> not sarcasm).
>>      
>
> 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.

>   * Where in the documentation do I have to change the description of
>     "--parents" option?
>    
You mean in a text editor, not within LyX? Just look for the string :-)
>   * When did the description of "--cc" for diff families last changed, by
>     whom and why?
>    
Ditto.
> Eas of doing these is mostly why we chose AsciiDoc to begin with.  Any
> alternative you are going to suggest should not make these two things
> impossible or very harder to do.
>    

If you ignore the LyX tags, you can just do what you are used to do without problem using a plain text editor. If you want to do something more complicated stuff like choosing a different environment or creating a nested enumerate list, it is easier to do that within LyX.

Abdel.
Previous: Junio C HamanoNext: Thomas Rast
Message 21 of 39 in “Git Community Book”
  1. Scott ChaconJul 29, 2008
  2. Miklos VajnaJul 29, 2008
  3. Petr BaudisJul 29, 2008
  4. Scott ChaconJul 29, 2008
  5. Junio C HamanoJul 29, 2008
  6. Julian PhillipsJul 29, 2008
  7. Junio C HamanoJul 29, 2008
  8. markdown 2 man, was Re: Git Community BookJohannes Schindelin, Jul 30, 2008
  9. Junio C HamanoJul 30, 2008
  10. Wincent ColaiutaJul 30, 2008
  11. Scott ChaconJul 31, 2008
  12. Junio C HamanoJul 31, 2008
  13. Abdelrazak YounesJul 31, 2008
  14. Stephan BeyerJul 31, 2008
  15. Abdelrazak YounesJul 31, 2008
  16. Abdelrazak YounesJul 31, 2008
  17. Miklos VajnaJul 31, 2008
  18. Abdelrazak YounesJul 31, 2008
  19. Miklos VajnaJul 31, 2008
  20. Junio C HamanoAug 1, 2008
  21. Abdelrazak YounesAug 1, 2008
  22. Thomas RastAug 1, 2008
  23. Abdelrazak YounesAug 1, 2008
  24. Jan KrügerJul 31, 2008
  25. Abdelrazak YounesAug 1, 2008
  26. Dmitry PotapovAug 1, 2008
  27. Abdelrazak YounesAug 1, 2008
  28. Scott ChaconJul 29, 2008
  29. Junio C HamanoJul 29, 2008
  30. J. Bruce FieldsJul 30, 2008
  31. Junio C HamanoJul 29, 2008
  32. Junio C HamanoJul 29, 2008
  33. Scott ChaconJul 29, 2008
  34. Scott ChaconJul 29, 2008
  35. Daniel BarkalowJul 29, 2008
  36. Junio C HamanoJul 29, 2008
  37. Bart TrojanowskiJul 30, 2008
  38. Junio C HamanoJul 30, 2008
  39. Bart TrojanowskiJul 30, 2008

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.