Re: [Slackbuilds-users] Suggestion: monospace font for README

2016-11-11 Thread Doogster
It's extremely common for software development projects to mandate maximum
line lengths as part of their coding standards. I suggest that SBo picks a
number that would look good without X, in a console with a "vga"
framebuffer, and then demands that contributors follow it.

On Thursday, 10 November 2016, B Watson  wrote:

> On 11/10/16, Erik Hanson > wrote:
>
> > It's not wrapping for me, there's plenty of room to the right of
> > the README text for bloodcm. Maybe you have some custom css, custom
> > font sizes, or need to reset your zoom?
>
> Yes, I increased the minimum font size in firefox ages ago, to a size
> that I can actually read without squinting.
>
> 710 pixels / 80 columns would be around 9px wide. Same as the IBM
> Monochrome Adaptor from 1981. But modern monitors have a lot smaller
> dot pitch than the ones from 1981...
>
> An annoying thing about the web (not singling out SBo site here) is
> columnar layouts. My monitor's 1920 pixels wide, but those READMEs
> only take up 710 pixels, or less than half the horizontal resolution,
> with 2 huge columns on either side wasting space. Lot of stuff like that
> out there.
>
> Not a web designer, so I don't have a fix for it. Just venting.
> ___
> SlackBuilds-users mailing list
> SlackBuilds-users@slackbuilds.org 
> http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/
>
>
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/



Re: [Slackbuilds-users] Suggestion: monospace font for README

2016-11-10 Thread B Watson
On 11/10/16, Erik Hanson  wrote:

> It's not wrapping for me, there's plenty of room to the right of
> the README text for bloodcm. Maybe you have some custom css, custom
> font sizes, or need to reset your zoom?

Yes, I increased the minimum font size in firefox ages ago, to a size
that I can actually read without squinting.

710 pixels / 80 columns would be around 9px wide. Same as the IBM
Monochrome Adaptor from 1981. But modern monitors have a lot smaller
dot pitch than the ones from 1981...

An annoying thing about the web (not singling out SBo site here) is
columnar layouts. My monitor's 1920 pixels wide, but those READMEs
only take up 710 pixels, or less than half the horizontal resolution,
with 2 huge columns on either side wasting space. Lot of stuff like that
out there.

Not a web designer, so I don't have a fix for it. Just venting.
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/



Re: [Slackbuilds-users] Suggestion: monospace font for README

2016-11-10 Thread Erik Hanson
On Thu, 10 Nov 2016 16:40:03 -0500
B Watson  wrote:

> Ugh. The new CSS stuff causes lines to break at about 66 characters
> for me, so READMEs that use line breaks at 72-75 characters come out
> like this:
> 
> Blood Crossmatching (formerly known as BloodTC) is a recreation of
> Blood
> (by Monolith Productions) for EDuke32 to bring all the fun and action
> of
> Blood to the EDuke32 port. This mod will be more powerful in the
> future,
> considering EDuke32 keeps getting better and better.
> 
> Which I could "fix" by using a smaller font for  in my browser,
> but it's already as small as it can be and still be readable (to me
> anyway).
> 
> Maybe we were better off before.

It's not wrapping for me, there's plenty of room to the right of
the README text for bloodcm. Maybe you have some custom css, custom
font sizes, or need to reset your zoom?


-- 
Erik
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/



Re: [Slackbuilds-users] Suggestion: monospace font for README

2016-11-10 Thread Ryan P.C. McQuen
On Thursday, November 10, 2016, B Watson  wrote:

> Ugh. The new CSS stuff causes lines to break at about 66 characters
> for me, so READMEs that use line breaks at 72-75 characters come out
> like this:
>
> Which I could "fix" by using a smaller font for  in my browser, but
> it's already as small as it can be and still be readable (to me anyway).
>


Isn't there some room to make the middle column wide enough to work for up
to 72 characters?

It is currently at 710 pixels, and even old and small screens should have
at least 768 pixels of width.


-- 
-Ryan
[ryanpcmcquen.org]
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/



Re: [Slackbuilds-users] Suggestion: monospace font for README

2016-11-10 Thread B Watson
Ugh. The new CSS stuff causes lines to break at about 66 characters
for me, so READMEs that use line breaks at 72-75 characters come out
like this:

Blood Crossmatching (formerly known as BloodTC) is a recreation of
Blood
(by Monolith Productions) for EDuke32 to bring all the fun and action
of
Blood to the EDuke32 port. This mod will be more powerful in the
future,
considering EDuke32 keeps getting better and better.

Which I could "fix" by using a smaller font for  in my browser, but
it's already as small as it can be and still be readable (to me anyway).

Maybe we were better off before.
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/



Re: [Slackbuilds-users] Suggestion: monospace font for README

2016-11-08 Thread Andrzej Telszewski

Hi,

Looks and reads good to me.
Thanks!

--
Best regards,
Andrzej Telszewski
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/



Re: [Slackbuilds-users] Suggestion: monospace font for README

2016-11-07 Thread Alexander Verbovetsky
On Mon, Nov 7, 2016, at 15:57, Ythogtha wrote:
> Put that style, it'll break a little the middle part, but not much, it'll
> be
> larger :
> #include div#wrap {
> background-color: #fff;
> margin-: 0 -100px;
> width: 910px;
> }
> If you want even larger, replace the -100px in the margin by a larger
> number,
> double its value, add it to 710 and that's your new width, example :
> #include div#wrap {
> background-color: #fff;
> margin-: 0 -200px;
> width: 1110px;
> }

Thank you very much for the idea!

I modified it to the following code that works perfectly in
chrome/userContent.css:

/* 
 * Force SBo to be wider
 */
@-moz-document domain(slackbuilds.org) {
  #parent, #include div#wrap {
width: 950px  !important;
background-color: #fff  !important; }
}

Best regards,
Alexander
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/



Re: [Slackbuilds-users] Suggestion: monospace font for README

2016-11-07 Thread Willy Sudiarto Raharjo
> This is mine: http://ejik.org/q/SBo-README-slalik-0.jpg

here's mine with same package
http://imgur.com/a/smIYx


-- 
Willy Sudiarto Raharjo



signature.asc
Description: OpenPGP digital signature
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/



Re: [Slackbuilds-users] Suggestion: monospace font for README

2016-11-07 Thread Ythogtha
> Hello,
> 
> I like the mono font for README, but I use a large font and for me lines
> are wrapped after 58 symbols.
> 
> On the other hand, the text is a narrow strip on my screen (1920x1200).
> Could it be possible to let the text use all available space in width?
> 
> If it's not feasible, maybe someone can suggest me what to put in my
> firefox's chrome/userContent.css to archive the same result?
> 
> Thank you in advance!

Put that style, it'll break a little the middle part, but not much, it'll be
larger :
#include div#wrap {
background-color: #fff;
margin-: 0 -100px;
width: 910px;
}
If you want even larger, replace the -100px in the margin by a larger number,
double its value, add it to 710 and that's your new width, example :
#include div#wrap {
background-color: #fff;
margin-: 0 -200px;
width: 1110px;
}

-- 
Arnaud 
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/



Re: [Slackbuilds-users] Suggestion: monospace font for README

2016-11-07 Thread Alexander Verbovetsky
> Also, since different people have different settings, i  think it
> would be good to include a screenshot link so that others can see how
> it's seen on other people's computer.

This is mine: http://ejik.org/q/SBo-README-slalik-0.jpg

Best regards,
Alexander
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/



Re: [Slackbuilds-users] Suggestion: monospace font for README

2016-11-07 Thread Willy Sudiarto Raharjo
> I like the mono font for README, but I use a large font and for me lines
> are wrapped after 58 symbols.
> 
> On the other hand, the text is a narrow strip on my screen (1920x1200).
> Could it be possible to let the text use all available space in width?

We will use the assumption users use default settings as most people do.
It's nearly impossible to accomodate every user's setting for their
browser preferences :)

Also, since different people have different settings, i  think it would
be good to include a screenshot link so that others can see how it's
seen on other people's computer.


-- 
Willy Sudiarto Raharjo



signature.asc
Description: OpenPGP digital signature
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/



Re: [Slackbuilds-users] Suggestion: monospace font for README

2016-11-07 Thread Alexander Verbovetsky
Hello,

I like the mono font for README, but I use a large font and for me lines
are wrapped after 58 symbols.

On the other hand, the text is a narrow strip on my screen (1920x1200).
Could it be possible to let the text use all available space in width?

If it's not feasible, maybe someone can suggest me what to put in my
firefox's chrome/userContent.css to archive the same result?

Thank you in advance!

Best regards,
Alexander
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/



Re: [Slackbuilds-users] Suggestion: monospace font for README

2016-11-06 Thread Fernando Lopez
can we have a smaller font? font size is too big at least for me...

On Sun, Nov 6, 2016 at 7:54 PM, B Watson  wrote:

> On 11/6/16, Willy Sudiarto Raharjo  wrote:
>
> > I have implemented a css code to fix the wrap issue, but feel free to
> > update the README
>
> Still worth doing, the READMEs with long lines look like crap in text
> editors or less (which to me is their native environment, not the web).
> ___
> SlackBuilds-users mailing list
> SlackBuilds-users@slackbuilds.org
> http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/
>
>


-- 


Regards,
Fernando Lopez Jr.
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/



Re: [Slackbuilds-users] Suggestion: monospace font for README

2016-11-06 Thread B Watson
On 11/6/16, Willy Sudiarto Raharjo  wrote:

> I have implemented a css code to fix the wrap issue, but feel free to
> update the README

Still worth doing, the READMEs with long lines look like crap in text
editors or less (which to me is their native environment, not the web).
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/



Re: [Slackbuilds-users] Suggestion: monospace font for README

2016-11-06 Thread Willy Sudiarto Raharjo
> I was about to comment that un-word-wrapped READMEs violate the
> guidelines, but went & looked first... and there's nothing in there
> about word-wrapping or max line length in the README.
>
> Maybe there should be?
>
> $ find . -name README | wc -l
> 6124
> $ find . -name README | xargs egrep -l
> '^.{81,}$'|wc -l
> 288
>
> Affects 5% of the builds. Shouldn't be too much work to fix, I'm willing
> to spend some time on it if you want. In theory, every maintainer should
> fix his own READMEs, but this is a cosmetic-only change, might be OK to
> just do it?

I have implemented a css code to fix the wrap issue, but feel free to
update the README

-- 
Willy Sudiarto Raharjo
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/



Re: [Slackbuilds-users] Suggestion: monospace font for README

2016-11-06 Thread Andrzej Telszewski

On 07/11/16 01:35, Willy Sudiarto Raharjo wrote:

You could also just use some CSS and have browsers wrap the text. Seems
much easier than editing a ton of READMES...

pre {
white-space: pre-wrap;   /* css-3 */
white-space: -moz-pre-wrap;  /* Mozilla, since 1999 */
white-space: -pre-wrap;  /* Opera 4-6 */
white-space: -o-pre-wrap;/* Opera 7 */
word-wrap: break-word;   /* Internet Explorer 5.5+ */
}

http://stackoverflow.com/questions/248011/how-do-i-wrap-text-in-a-pre-tag

Any reasonably modern browser will not need a prefix, meaning you could
simplify the CSS to:

pre {
  white-space: pre-wrap;}


https://developer.mozilla.org/en-US/docs/Web/CSS/white-space#Browser_compatibility


I implemented this proposal (wrapping issue) just now
can anyone review the results in
https://slackbuilds.org/repository/14.2/multimedia/ExMplayer/ ?



Works for me (SeaMonkey 2.40).


The content of the README will be using  and it looks different
from the rest of the page (deps, maintainer, etc).




___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/




--
Best regards,
Andrzej Telszewski
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/



Re: [Slackbuilds-users] Suggestion: monospace font for README

2016-11-06 Thread Willy Sudiarto Raharjo
>> You could also just use some CSS and have browsers wrap the text. Seems
>> much easier than editing a ton of READMES...
>>
>> pre {
>> white-space: pre-wrap;   /* css-3 */
>> white-space: -moz-pre-wrap;  /* Mozilla, since 1999 */
>> white-space: -pre-wrap;  /* Opera 4-6 */
>> white-space: -o-pre-wrap;/* Opera 7 */
>> word-wrap: break-word;   /* Internet Explorer 5.5+ */
>> }
>>
>> http://stackoverflow.com/questions/248011/how-do-i-wrap-text-in-a-pre-tag
>>
>> Any reasonably modern browser will not need a prefix, meaning you could
>> simplify the CSS to:
>>
>> pre {
>>   white-space: pre-wrap;}
>>
>>
>> https://developer.mozilla.org/en-US/docs/Web/CSS/white-space#Browser_compatibility

I implemented this proposal (wrapping issue) just now
can anyone review the results in
https://slackbuilds.org/repository/14.2/multimedia/ExMplayer/ ?

The content of the README will be using  and it looks different
from the rest of the page (deps, maintainer, etc).


-- 
Willy Sudiarto Raharjo



signature.asc
Description: OpenPGP digital signature
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/



Re: [Slackbuilds-users] Suggestion: monospace font for README

2016-11-06 Thread Jeremy Hansen
Yeah, it just covers any browsers that might not (which probably wouldn't
be frequently used by Slackware users).

On Sun, Nov 6, 2016, 6:14 PM Ryan P.C. McQuen  wrote:

> On Sun, Nov 6, 2016 at 2:48 PM Jeremy Hansen jebrhansen+...@gmail.com
>  wrote:
>
> You could also just use some CSS and have browsers wrap the text. Seems
> much easier than editing a ton of READMES...
>
> pre {
> white-space: pre-wrap;   /* css-3 */
> white-space: -moz-pre-wrap;  /* Mozilla, since 1999 */
> white-space: -pre-wrap;  /* Opera 4-6 */
> white-space: -o-pre-wrap;/* Opera 7 */
> word-wrap: break-word;   /* Internet Explorer 5.5+ */
> }
>
> http://stackoverflow.com/questions/248011/how-do-i-wrap-text-in-a-pre-tag
>
> Any reasonably modern browser will not need a prefix, meaning you could
> simplify the CSS to:
>
> pre {
>   white-space: pre-wrap;}
>
>
> https://developer.mozilla.org/en-US/docs/Web/CSS/white-space#Browser_compatibility
> ​
> ___
> SlackBuilds-users mailing list
> SlackBuilds-users@slackbuilds.org
> http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/
>
>
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/



Re: [Slackbuilds-users] Suggestion: monospace font for README

2016-11-06 Thread Ryan P.C. McQuen
On Sun, Nov 6, 2016 at 2:48 PM Jeremy Hansen jebrhansen+...@gmail.com
 wrote:

You could also just use some CSS and have browsers wrap the text. Seems
> much easier than editing a ton of READMES...
>
> pre {
> white-space: pre-wrap;   /* css-3 */
> white-space: -moz-pre-wrap;  /* Mozilla, since 1999 */
> white-space: -pre-wrap;  /* Opera 4-6 */
> white-space: -o-pre-wrap;/* Opera 7 */
> word-wrap: break-word;   /* Internet Explorer 5.5+ */
> }
>
> http://stackoverflow.com/questions/248011/how-do-i-wrap-text-in-a-pre-tag
>
Any reasonably modern browser will not need a prefix, meaning you could
simplify the CSS to:

pre {
  white-space: pre-wrap;}

https://developer.mozilla.org/en-US/docs/Web/CSS/white-space#Browser_compatibility
​
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/



Re: [Slackbuilds-users] Suggestion: monospace font for README

2016-11-06 Thread Jeremy Hansen
You could also just use some CSS and have browsers wrap the text. Seems
much easier than editing a ton of READMES...

pre {
white-space: pre-wrap;   /* css-3 */
white-space: -moz-pre-wrap;  /* Mozilla, since 1999 */
white-space: -pre-wrap;  /* Opera 4-6 */
white-space: -o-pre-wrap;/* Opera 7 */
word-wrap: break-word;   /* Internet Explorer 5.5+ */
}

http://stackoverflow.com/questions/248011/how-do-i-wrap-text-in-a-pre-tag

On Sun, Nov 6, 2016, 5:41 PM B Watson  wrote:

> On 11/6/16, Erik Hanson  wrote:
>
> > If you want to push a branch that's just cosmetic fixes, I think we
> > could merge it.
>
> OK, working on it now, branch will be called user/urchlay/cosmetics.
> ___
> SlackBuilds-users mailing list
> SlackBuilds-users@slackbuilds.org
> http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/
>
>
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/



Re: [Slackbuilds-users] Suggestion: monospace font for README

2016-11-06 Thread B Watson
On 11/6/16, Erik Hanson  wrote:

> If you want to push a branch that's just cosmetic fixes, I think we
> could merge it.

OK, working on it now, branch will be called user/urchlay/cosmetics.
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/



Re: [Slackbuilds-users] Suggestion: monospace font for README

2016-11-06 Thread Erik Hanson
On Sun, 6 Nov 2016 15:47:56 -0500
B Watson  wrote:

> I was about to comment that un-word-wrapped READMEs violate the
> guidelines, but went & looked first... and there's nothing in there
> about word-wrapping or max line length in the README.
> 
> Maybe there should be?

I agree.

> Affects 5% of the builds. Shouldn't be too much work to fix, I'm
> willing to spend some time on it if you want. In theory, every
> maintainer should fix his own READMEs, but this is a cosmetic-only
> change, might be OK to just do it?

If you want to push a branch that's just cosmetic fixes, I think we
could merge it.


-- 
Erik
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/



Re: [Slackbuilds-users] Suggestion: monospace font for README

2016-11-06 Thread Ryan P.C. McQuen
>
>
> That's IMHO why Markdown would be the best solution for README files.
>

I am a big fan of Markdown. How much support is needed? If we only want to
be able to have code snippets, I wrote a really lightweight JavaScript
library to parse text and syntax highlight blocks of code like this:

```sh
#!/bin/sh
slackpkg_update_only() {
  slackpkg update gpg
  slackpkg update
}
```

It ends up looking something like the attached image.[image: Screenshot at
2016-11-06 13:00:26.png]

https://github.com/ryanpcmcquen/codeFormatter

If we only need code snippet support, this may be easier to integrate than
a full fledged markdown parser (if people are even onboard with that).
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/



Re: [Slackbuilds-users] Suggestion: monospace font for README

2016-11-06 Thread Thomas Szteliga
On 11/06/2016 09:47 PM, B Watson wrote:
> On 11/6/16, Erik Hanson  wrote:
>> I've made the change. Not sure what I think about it. Instantly I can
>> see some README files are not word wrapped properly:
>> https://slackbuilds.org/repository/14.2/multimedia/ExMplayer/
> Yuck.
> I was about to comment that un-word-wrapped READMEs violate the
> guidelines, but went & looked first... and there's nothing in there
> about word-wrapping or max line length in the README.
> Maybe there should be?


Definitely. Max line length should be mandatory.


> $ find . -name README | wc -l
> 6124
> $ find . -name README | xargs egrep -l
> '^.{81,}$'|wc -l
> 288
> Affects 5% of the builds. Shouldn't be too much work to fix, I'm willing
> to spend some time on it if you want. In theory, every maintainer should
> fix his own READMEs, but this is a cosmetic-only change, might be OK to
> just do it?
> Some of them are formatted OK, except they have URLs that are too
> long. Not much can be done about that.



That's IMHO why Markdown would be the best solution for README files.


-- 
Thomas Szteliga




smime.p7s
Description: S/MIME Cryptographic Signature
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/



Re: [Slackbuilds-users] Suggestion: monospace font for README

2016-11-06 Thread B Watson
On 11/6/16, Erik Hanson  wrote:

> I've made the change. Not sure what I think about it. Instantly I can
> see some README files are not word wrapped properly:
> https://slackbuilds.org/repository/14.2/multimedia/ExMplayer/

Yuck.

I was about to comment that un-word-wrapped READMEs violate the
guidelines, but went & looked first... and there's nothing in there
about word-wrapping or max line length in the README.

Maybe there should be?

$ find . -name README | wc -l
6124
$ find . -name README | xargs egrep -l
'^.{81,}$'|wc -l
288

Affects 5% of the builds. Shouldn't be too much work to fix, I'm willing
to spend some time on it if you want. In theory, every maintainer should
fix his own READMEs, but this is a cosmetic-only change, might be OK to
just do it?

Some of them are formatted OK, except they have URLs that are too
long. Not much can be done about that.
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/



Re: [Slackbuilds-users] Suggestion: monospace font for README

2016-11-06 Thread Thomas Szteliga
On 11/06/2016 08:56 PM, Erik Hanson wrote:
> I've made the change. Not sure what I think about it. Instantly I can
> see some README files are not word wrapped properly:
> https://slackbuilds.org/repository/14.2/multimedia/ExMplayer/
> It's probably smart to keep it though:
> https://slackbuilds.org/repository/14.2/multimedia/JSampler/


I don't think ACII-art should be supported ;-)
But if that's really needed the maintainer of JSampler
will be able to achieve this using Markdown.

So Markdown +1.


-- 
Thomas Szteliga




smime.p7s
Description: S/MIME Cryptographic Signature
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/



Re: [Slackbuilds-users] Suggestion: monospace font for README

2016-11-06 Thread Andrzej Telszewski

On 06/11/16 20:56, Erik Hanson wrote:

On Sun, 6 Nov 2016 20:16:23 +0100
Andrzej Telszewski  wrote:


Hi,

I think it would make sense to have README enclosed within
 tags, having monospace font.

Otherwise, when using GUI web browser, we lose all the text
formatting the maintainers do.


I've made the change. Not sure what I think about it. Instantly I can
see some README files are not word wrapped properly:
https://slackbuilds.org/repository/14.2/multimedia/ExMplayer/
It's probably smart to keep it though:
https://slackbuilds.org/repository/14.2/multimedia/JSampler/




That was fast :-)
Let's give it a try, because at first sight it looks strange.


--
Best regards,
Andrzej Telszewski
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/



Re: [Slackbuilds-users] Suggestion: monospace font for README

2016-11-06 Thread Erik Hanson
On Sun, 6 Nov 2016 20:16:23 +0100
Andrzej Telszewski  wrote:

> Hi,
> 
> I think it would make sense to have README enclosed within
>  tags, having monospace font.
> 
> Otherwise, when using GUI web browser, we lose all the text
> formatting the maintainers do.

I've made the change. Not sure what I think about it. Instantly I can
see some README files are not word wrapped properly:
https://slackbuilds.org/repository/14.2/multimedia/ExMplayer/
It's probably smart to keep it though:
https://slackbuilds.org/repository/14.2/multimedia/JSampler/


-- 
Erik
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/



[Slackbuilds-users] Suggestion: monospace font for README

2016-11-06 Thread Andrzej Telszewski

Hi,

I think it would make sense to have README enclosed within  
tags, having monospace font.


Otherwise, when using GUI web browser, we lose all the text formatting 
the maintainers do.


--
Best regards,
Andrzej Telszewski
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/