Skip to content
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.

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

Handle multiple files #40

Open
ScreamingDev opened this issue Aug 24, 2013 · 4 comments
Open

Handle multiple files #40

ScreamingDev opened this issue Aug 24, 2013 · 4 comments

Comments

@ScreamingDev
Copy link

Situation

  • Gimli handles all Markdown in the folder
  • Gimli handles one Markdown in the folder

Problem

  • Gimli does not handle 2,3,4,... files only

Solution

  • Let -f take more than one file (gimli -f two.md three.md one.md)
  • or let be there multiple -f (gimli -f two.md -f three.md -f one.md)
@walle
Copy link
Owner

walle commented Sep 21, 2013

I'll look into this.

@floere
Copy link

floere commented Mar 30, 2015

This would be great to have. @walle Have you looked into it by any chance?

@walle
Copy link
Owner

walle commented Mar 30, 2015

Yes, I have, the thing is that I haven't had time (motivation really) to implement the feature.

The design of gimli is kind of broken from the start, I wrote it to be able to quickly generate nice pdfs for some reports that I was writing, and the use case then was to generate all files, or just one.

A better approach had been to use the common unix way eg. cp SOURCE... DIRECTORY like mdpdf (https://github.com/walle/mdpdf#usage) does. To take one or many files (or stdin) and write it to a file (or stdout). This gives a lot more flexibility and makes it possible to chain the application using pipes, which would be nice. Please note that the mdpdf application is a quick project I wrote to get back my C legs and doesn't have all the features gimli does.

I have started writing a specification that should take into account all the use cases and properly document the features available, I have some work to do left though. But my idea is to ask the community (~350 stars so hopefully I will get some response) to read the specification and improve on it. When the specification is set implement it. The specification would give some structure to the development, eg. changes would be discussed in regards to the spec before implementing them. The more structured development (I think) would give me more motivation to work on the project.

So this change would enable this feature (and give some extra perks).

@floere
Copy link

floere commented Apr 15, 2015

Thanks for your explanation :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants