li.inline,
.inline-list > li { display: inline; }
li.inline:before,
.inline-list > li:before { content:" | " }
ul.inline-list { display: inline; margin: 0; padding: 0; }
[download]

Thanks for the instructions - though I'm not quite sure where to put the modified stylesheet for it to take effect (for anonymous visitors).

Anyhow, why not leave the defaults as they were, an have those monks who like the new layout make the respective settings in their private CSS?

User Contributed Style Sheets for Perlmonks and PM Stylesheet on local filesystem? WORKS! have instructions and more links to how to keep the CSS as you like it. Also, through themes for Anonymous Monk or try out themes without changing display settings, you should be able to load even more custom data.

No need to copy common.css, just add personal CSS to override the parts one wants to change. (How to customize CSS when anonymous is "not our problem". If you want easy customization, then log in; that's the purpose of logging in. If you log in, then you can even add JS that makes it so that when you post, it gets posted anonymously.)

The "(*)" for the link to Tidings in the "Information" nodelet was in the wrong place and has been moved. At least many of the unclosed LI tags have also been fixed.

It looks like jdporter was going for standardizing the style of "lists of link" with a distinction between "internal" links and "external" links. I much prefer the "| a | b | c" style for list of links that use very short title like is the case in some cabal-only nodelets.

I agree that the auto-wrapping "| a link to one thing | some other link to another | yet another link to something else" style is a worse choice for non-terse link descriptions like many of the links found in the "Information" nodelet.

So we probably need separate CSS classes for "terse lists" vs "non-terse lists".

It looks like some of the patches were applied before they were fully polished. But then, that's sometimes a good way to get decent feedback on the proposed changes.

Yes, the intent is indeed to use " | " in front of each link, at least for compact lists.

Yes, the intent is indeed to use " | " in front of each link, at least for compact lists.

But why before the first element in the list?? It gives the perception of sloppy coding and aesthetically it looks horrible.

Elda Taluta; Sarks Sark; Ark Arks

And no * next to Tidings to indicate an update either. :-/

Maybe I'm the only one, ...

apparently, that's the case (or almost - thanks Argel!). Or monks don't dare to speak up because they might fall into disgrace before the Gods. That would be pretty sad. Whatever. Congratulations on having made the default appearance of the site not only a little more ugly, but also less easy to navigate.

Oh well, if that's what people seem to like, I'll see if can remember to give any code I post the same fancy new looks.

| #!/usr/bin/perl | use strict; | use
warnings; | my $fname = 'foo.txt'; | open
my $fh, '<', $fname or die "Couldn't open
'$fname': $!; | while (my $line = <$fh>)
{ | if ($line =~ /^\s*bar\z/) { | ...
[download]

Bon appétit! :)

Or there's just not as much activity going on because it's the Thanksgiving holiday extended weekend here in the 'States. Bad time to post new code and a bad time to complain about it! :-/

With that said, I find it hard to believe that the intent is to start with a "|". And I noticed that "HTML error reporting during Preview" shows missing </li> tags after every link in every nodelet using the new layout. Maybe someone accidentally pushed some code out -- or pushed the wrong code out). Whatever happened, "rush job" definitely comes to mind.

Elda Taluta; Sarks Sark; Ark Arks

Thank you sincerely for your feedback. It is much appreciated. It's definitely better than being "warnocked". :-)

Whatever happened, "rush job" definitely comes to mind.

Now that, I have to take at least a little bit of exception to. On the gripping hand, you have to remember that we have no dev site. The only way to try any changes of any consequence is to alter the live site. If it turns out that a patch breaks things, or is considered regressive by most monks, then we can roll it back. On the loosing hand, making the grand change I had in mind — which necessarily involved numerous patches and doc edits — could not be done even remotely atomically; it took days. And I carefully examined the effects of each one, trying to calculate how it contributed to the desired trajectory. Understanding that between the moment the first alteration is made and the grand change is finally complete the site is in some sense "broken", I did my best to do it all as quickly as possible, while being careful not to miss any unexpected side-effects.

I find it hard to believe that the intent is to start with a "|"

It's not really so unbelievable, is it? I think you could get used to it in about 2 days. In any case, if you really hate it, you can get rid of the first "|" through css.

What is the sound of Windows? Is it not the sound of a wall upon which people have smashed their heads... all the way through?

If your code would be on every page, and always the same, I rather have it that way that using more screen space.

Not that I care much how Find Nodes is formatted. I seldomly use it, and it isn't that the gained screen estate is being reused by something else (in my case, the freed up screen space is just white).