All of lore.kernel.org
 help / color / mirror / Atom feed
From: Abdelrazak Younes <younes@lyx.org>
To: Junio C Hamano <gitster@pobox.com>
Cc: Stephan Beyer <s-beyer@gmx.net>,
	git@vger.kernel.org,
	Johannes Schindelin <Johannes.Schindelin@gmx.de>,
	Julian Phillips <julian@quantumfyre.co.uk>,
	Scott Chacon <schacon@gmail.com>, Petr Baudis <pasky@suse.cz>
Subject: Re: markdown 2 man, was Re: Git Community Book
Date: Fri, 01 Aug 2008 09:11:16 +0200	[thread overview]
Message-ID: <4892B714.8010401@lyx.org> (raw)
In-Reply-To: <7vvdylv9zq.fsf@gitster.siamese.dyndns.org>

[-- Attachment #1: Type: text/plain, Size: 1496 bytes --]

Junio C Hamano wrote:
> 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.


[-- Attachment #2: FAQ.lyx --]
[-- Type: application/lyx, Size: 35350 bytes --]

  reply	other threads:[~2008-08-01  7:12 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-29 16:20 Git Community Book Scott Chacon
2008-07-29 16:28 ` Miklos Vajna
2008-07-29 17:09 ` Petr Baudis
2008-07-29 18:30   ` Scott Chacon
2008-07-29 18:42     ` Junio C Hamano
2008-07-29 19:00       ` Julian Phillips
2008-07-29 19:09         ` Junio C Hamano
2008-07-30 13:27         ` markdown 2 man, was " Johannes Schindelin
2008-07-30 19:32           ` Junio C Hamano
2008-07-30 23:48             ` Wincent Colaiuta
2008-07-31  0:13               ` Scott Chacon
2008-07-31  0:30               ` Junio C Hamano
2008-07-31 11:24             ` Abdelrazak Younes
2008-07-31 13:01               ` Stephan Beyer
2008-07-31 14:13                 ` Abdelrazak Younes
2008-07-31 14:33                 ` Abdelrazak Younes
2008-07-31 15:09                   ` Miklos Vajna
2008-07-31 15:29                     ` Abdelrazak Younes
2008-07-31 19:00                       ` Miklos Vajna
2008-08-01  0:45                   ` Junio C Hamano
2008-08-01  7:11                     ` Abdelrazak Younes [this message]
2008-08-01  9:46                       ` Thomas Rast
2008-08-01 10:19                         ` Abdelrazak Younes
2008-07-31 20:57               ` Jan Krüger
2008-08-01  7:50                 ` Abdelrazak Younes
2008-08-01 10:45                   ` Dmitry Potapov
2008-08-01 11:06                     ` Abdelrazak Younes
2008-07-29 19:34       ` Scott Chacon
2008-07-29 19:57         ` Junio C Hamano
2008-07-30 21:39     ` J. Bruce Fields
2008-07-29 17:43 ` Junio C Hamano
2008-07-29 18:25   ` Junio C Hamano
2008-07-29 19:29     ` Scott Chacon
2008-07-29 19:24   ` Scott Chacon
2008-07-29 22:34 ` Daniel Barkalow
2008-07-29 22:47   ` Junio C Hamano
2008-07-30 13:20     ` Bart Trojanowski
2008-07-30 18:27       ` Junio C Hamano
2008-07-30 13:31     ` Bart Trojanowski

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4892B714.8010401@lyx.org \
    --to=younes@lyx.org \
    --cc=Johannes.Schindelin@gmx.de \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=julian@quantumfyre.co.uk \
    --cc=pasky@suse.cz \
    --cc=s-beyer@gmx.net \
    --cc=schacon@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.