# Git doc generation question

3 messages from 2010-11-19 to 2010-11-19. Participants: Pascal Obry, Drew Northup.
Thread: https://gitlist.dev/t/25790

## Pascal Obry, 2010-11-19 16:26

Subject: Git doc generation question
Message-ID: <4CE6A53A.9090203@obry.net>
URL: https://gitlist.dev/e/4CE6A53A.9090203%40obry.net

```

Hi,

I'm building Git from source and in the documentation I have some code
remaining, for example:

   $ man git

git me in the CONFIGURATION MECHANISM section:


<<
       example:

           .ft C
           #
           # A '#' or ';' character indicates a comment.
           #

           ; core variables
           ...
           .ft
>>

It looks like the ".ft C" and the ending .ft are some code not properly
parsed. Right?

Is that a known issue?

I had this problem on Cygwin and now on GNU/Debian!

Thanks,
Pascal.

-- 

--|------------------------------------------------------
--| Pascal Obry                           Team-Ada Member
--| 45, rue Gabriel Peri - 78114 Magny Les Hameaux FRANCE
--|------------------------------------------------------
--|    http://www.obry.net  -  http://v2p.fr.eu.org
--| "The best way to travel is by means of imagination"
--|
--| gpg --keyserver keys.gnupg.net --recv-key F949BD3B

```

## Drew Northup, 2010-11-19 16:47

Subject: Re: Git doc generation question
Message-ID: <1290185252.13785.1.camel@drew-northup.unet.maine.edu>
URL: https://gitlist.dev/e/1290185252.13785.1.camel%40drew-northup.unet.maine.edu
In-Reply-To: <4CE6A53A.9090203@obry.net>

```

On Fri, 2010-11-19 at 17:26 +0100, Pascal Obry wrote:
> Hi,
> 
> I'm building Git from source and in the documentation I have some code
> remaining, for example:
> 
>    $ man git
> 
> git me in the CONFIGURATION MECHANISM section:
> 
> 
> <<
>        example:
> 
>            .ft C
>            #
>            # A '#' or ';' character indicates a comment.
>            #
> 
>            ; core variables
>            ...
>            .ft
> >>
> 
> It looks like the ".ft C" and the ending .ft are some code not properly
> parsed. Right?
> 
> Is that a known issue?
> 
> I had this problem on Cygwin and now on GNU/Debian!
> 
> Thanks,
> Pascal.

Pascal,
Have a look at this thread:
http://article.gmane.org/gmane.comp.version-control.git/161607


-- 
-Drew Northup N1XIM
   AKA RvnPhnx on OPN
________________________________________________
"As opposed to vegetable or mineral error?"
-John Pescatore, SANS NewsBites Vol. 12 Num. 59

```

## Pascal Obry, 2010-11-19 17:02

Subject: Re: Git doc generation question
Message-ID: <4CE6ADB7.7020604@obry.net>
URL: https://gitlist.dev/e/4CE6ADB7.7020604%40obry.net
In-Reply-To: <1290185252.13785.1.camel@drew-northup.unet.maine.edu>

```
Drew,

> Have a look at this thread:
> http://article.gmane.org/gmane.comp.version-control.git/161607

Thanks a lot working for me!

-- 

--|------------------------------------------------------
--| Pascal Obry                           Team-Ada Member
--| 45, rue Gabriel Peri - 78114 Magny Les Hameaux FRANCE
--|------------------------------------------------------
--|    http://www.obry.net  -  http://v2p.fr.eu.org
--| "The best way to travel is by means of imagination"
--|
--| gpg --keyserver keys.gnupg.net --recv-key F949BD3B

```