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

Viewing Enhancement #1

Open
AndrewRussellHayes opened this issue Jan 18, 2015 · 9 comments
Open

Viewing Enhancement #1

AndrewRussellHayes opened this issue Jan 18, 2015 · 9 comments

Comments

@AndrewRussellHayes
Copy link

I wonder if there is a short&simple way to view the journal once it gets long? something similar to the way man pages are viewed?

Anyway, regardless, great idea! I'm already using it!

@gopatrik
Copy link
Owner

Good point!

Since it's markdown - the first thing that comes to mind is just a css file that formats the html in a really good way; could also build in some pagination.

I've also considered the idea to sort the file by newest first, so the most relevant info is always at the top, I guess the sooner I can come to terms with this the better. What do you think?

Not sure what you mean by how man pages are viewed though?

Cool! Thank you! Me too! Spread the love! :)

@AndrewRussellHayes
Copy link
Author

When i was referring to man pages I was meaning the pagination you referred to.

@lindskogen
Copy link

@AndrewRussellHayes manpages are viewed per default by less, try using less ajour.md?

@AndrewRussellHayes
Copy link
Author

@Ndushi perfect. exactly what i was looking for.

@gopatrik do you think it would make sense for ajour, when called with no arguments, to perform less ajour.md ?

It seems to me that viewing the journal is a sensible default for ajour when called without a statement to journal or add to an already existing journal.

Thoughts?

@gopatrik
Copy link
Owner

@AndrewRussellHayes @Ndushi Great idea, will take care of it when I get home, (if I don't see a pull request by then) ;)!

@AndrewRussellHayes
Copy link
Author

If I get a chance I'll try my hand at it. Wrestling with an Ubuntu preseed file at the moment.

  • Andrew Hayes
    615.351.5116
    linkedin.com/in/AndrewRussellHayes

On Mon, Jan 19, 2015 at 10:53 AM, Patrik Göthe notifications@github.com
wrote:

@AndrewRussellHayes @Ndushi Great idea, will take care of it when I get home, (if I don't see a pull request by then) ;)!

Reply to this email directly or view it on GitHub:
#1 (comment)

@gopatrik
Copy link
Owner

@AndrewRussellHayes Hm. Not as trivial as I thought to run a shell command in the current session for node. First I looked into shelljs, but couldn't keep the less process alive, just got a huge output dump before the program exits. Now I'm looking into require('child_process').spawn. http://nodejs.org/api/child_process.html#child_process_child_process_spawn_command_args_options

@AndrewRussellHayes
Copy link
Author

Do you have any thoughts on a different language?

I made a fork and was going to re-write using go. Mainly because I want to get some go practice and I thought it would be nice to exist without any dependancies.

Do you know much about go? its a great language and It should allow the shell executions we are discussing here.

@gopatrik
Copy link
Owner

@AndrewRussellHayes Haha, that's ironic, I wrote this as an npm package so I could learn to to just that.

I've tried out a few go-exercises, but never got around to creating a project in it!

I'll give it some thought, you are more than welcome to give it a go though. Pun intended!

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