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

A better format for email digest #8

Open
omerisimo opened this issue Feb 17, 2013 · 2 comments
Open

A better format for email digest #8

omerisimo opened this issue Feb 17, 2013 · 2 comments

Comments

@omerisimo
Copy link
Contributor

The email digest format contains the posts subject and the full body.
This results in a very long email.
I think it is better to include on the first line/x words of the post body.
Original:

Gemfile dependency graph _by Daniel Salmeron Amselem_
Although you could use the Gemfile.lock to track dependencies between different gems, there's also a more graphical and nice way to see such information.
brew install graphviz && gem install ruby-graphviz && bundle viz
Take a look at the Bundler documentation for more information about the bundle viz command.

Suggestion:

Gemfile dependency graph _by Daniel Salmeron Amselem_
Although you could use the Gemfile.lock to track dependencies between different gems...

Any thoughts? suggestions?

@damselem
Copy link
Owner

I like the idea but in order to implement such solution I would like to know how do you think we should do it.

The two solutions I have in mind are:

  • Show the whole first sentence.

    Gemfile dependency graph _by Daniel Salmeron Amselem_
    Although you could use the Gemfile.lock to track dependencies between different gems, there's also a more graphical and nice way to see such information.

  • Specify a maximum number of words. For example (max_words: 10)

    Gemfile dependency graph _by Daniel Salmeron Amselem_
    Although you could use the Gemfile.lock to track dependencies between...

@omerisimo
Copy link
Contributor Author

I think it should be the (sentence.first) OR (max_words: ~20)

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

No branches or pull requests

2 participants