Re: [FFmpeg-devel] [PATCH 1/6] docs: add missing code formatting around commands

2014-09-12 Thread Lou Logan
On Fri, 12 Sep 2014 20:06:47 +0200, James Darnley wrote: > Should I go through the file(s) and change other codes to commands where > they are really commands? (This would be a separate patch.) Personally I wouldn't bother, but it's up to you. IIRC, the docs in general are somewhat inconsistent

Re: [FFmpeg-devel] [PATCH 1/6] docs: add missing code formatting around commands

2014-09-12 Thread Timothy Gu
On Fri, Sep 12, 2014 at 11:06 AM, James Darnley wrote: > On 2014-09-12 01:33, Timothy Gu wrote: >> On Thu, Sep 11, 2014 at 4:31 PM, James Darnley >> wrote: >>> --- >>> doc/developer.texi | 6 +++--- >>> 1 file changed, 3 insertions(+), 3 deletions(-) >> >> I would use @command{}. > > I will cha

Re: [FFmpeg-devel] [PATCH 1/6] docs: add missing code formatting around commands

2014-09-12 Thread James Darnley
On 2014-09-12 01:33, Timothy Gu wrote: > On Thu, Sep 11, 2014 at 4:31 PM, James Darnley > wrote: >> --- >> doc/developer.texi | 6 +++--- >> 1 file changed, 3 insertions(+), 3 deletions(-) > > I would use @command{}. I will change it to command. Should I go through the file(s) and change othe

Re: [FFmpeg-devel] [PATCH 1/6] docs: add missing code formatting around commands

2014-09-11 Thread Timothy Gu
On Thu, Sep 11, 2014 at 4:31 PM, James Darnley wrote: > --- > doc/developer.texi | 6 +++--- > 1 file changed, 3 insertions(+), 3 deletions(-) I would use @command{}. [...] Timothy ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.o