8000 Ta/asciidoc by ThomasFunk · Pull Request #1 · ThomasAdam/fvwm · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

Ta/asciidoc #1

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Open
wants to merge 16 commits into
base: ta/asciidoc
Choose a base branch
from
Open

Ta/asciidoc #1

wants to merge 16 commits into from

Conversation

ThomasFunk
Copy link

Hi Thomas,

here's my first package :)

Could you please check the TODO that all FvwmModules listed (without the made ones).

Also check the format conventions file if something missed or should be changed.

Thanks,
Thomas

@ThomasFunk
new file: FvwmModules/FvwmAnimate.txt
4dbfd7c 
new file:   FvwmModules/FvwmAuto.txt
new file:   FvwmModules/FvwmBacker.txt
new file:   FvwmModules/FvwmBanner.txt
new file:   FvwmModules/FvwmButtons.txt
@ThomasFunk
New FvwmModules manpages A-D
b06e2f9
@ThomasFunk
FvwmModules TODO list
03869c4
@ThomasFunk
Add format conventions docu to use with creating manpages
ea3552d
@ThomasAdam
Copy link
Owner

On Sat, Feb 25, 2012 at 06:54:52AM -0800, Thomas Funk wrote:

Hi Thomas,

here's my first package :)

Thanks. Will take a look on Monday.

-- Thomas Adam

"Deep in my heart I wish I was wrong. But deep in my heart I know I am
not." -- Morrissey ("Girl Least Likely To" -- off of Viva Hate.)

@ThomasFunk
Copy link
Author

Hi Thomas,
I've finished the manpages for FvwmModules except the files listed in TODO.

FYI:
All files are reviewed as html also (for future use).

@ghost ghost assigned ThomasAdam Mar 17, 2012
@ThomasAdam
Copy link
Owner

Also, can you add a new top-level "fvwmmodules.txt" which includes the files from the FvwmModules/ directory, so that make_sections.sh will work correctly?

@ThomasFunk
Copy link
Author

I could do that but this will destroy the manpage structure recommended by asciidoc. Furthermore this will get a "huge" manpage and it will make problems with the html creation (ok this is perhaps not interesting now but should be bear in mind ...). I would rather change the make_sections.sh like this:
for file in egrep -rl -e "^:doctype: manpage" * --exclude-dir=sample
do
a2x -vf manpage $file
done

Then the manpages will create in the subfolders, too.

@ThomasAdam
Copy link
Owner

On 18 March 2012 13:14, Thomas Funk
reply@reply.github.com
wrote:

I could do that but this will destroy the manpage structure recommended by asciidoc. Furthermore this will get a "huge" manpage and it will make problems with the html creation (ok this is perhaps not interesting now but should be bear in mind ...). I would rather change the make_sections.sh like this:

That doesn't matter. See "man zshall" for instance. I still want
that ability, even for modules.

for file in egrep -rl -e "^:doctype: manpage" * --exclude-dir=sample

No, no. That's not correct at all. Use find(1). I'll fix this up locally.

-- Thomas Adam

@ThomasFunk
Copy link
Author

ok, I've created a FvwmModules.txt with all FvmModules except fvwm-bug.txt, fvwm-convert-2.4.txt, fvwm-convert-2.6.txt and fvwm-config.txt. Are these also modules? Or should we create a seperate manpage e.g fvwm-convert.txt or so ... ?

@ThomasFunk
Copy link
Author

I've created a utility manpage. Some scripts are missing. See the TODO in FvwmUtils folder.

@ThomasAdam
Copy link
Owner

I'd rather you didn't do this. Unlike modules, for instance, there is no commonality with the programs you've grouped together as being "utilities". Please drop this, but keep the commands under the FvwmUtils/ directory, and they'll get picked up automatically by my changes to make_sections.sh without needing fvwmutils.txt at all.

@ThomasFunk
Copy link
Author

Done.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees

@ThomasAdam ThomasAdam

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
2 participants
@ThomasFunk @ThomasAdam
0