default monospaced code font

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
105 messages Options
1 ... 3456
Reply | Threaded
Open this post in threaded view
|

Re: default monospaced code font

EstebanLM
yes, that's because I failed to configure the new fonts and system fallbacks to the default font... to everything.
anyway I switched back, while I see why font changes are not taken into account.

no log needed :)

On Oct 17, 2013, at 7:53 PM, [hidden email] wrote:

> Not sure if anyone noticed this previously, but I had a problem with Monticello repositories not showing the usual convention to bold and underline items to indicate which were in the image - and tracked this down to being introduced between builds #30469 and #30470.  Coincidently this is where the default font seemed to change from DejaVu to Source Code Pro.  Looks like the default is back to DejaVi in build #30497, so I'm not sure what you'd like to do about logging this as an issue.
>
> cheers -ben
>


Reply | Threaded
Open this post in threaded view
|

Re: default monospaced code font

NorbertHartl
97 (..well…98) mails in one thread is quite a number. So fonts seems to be the biggest concern these days. That could say something about pharo ;)

Norbert
Am 17.10.2013 um 19:58 schrieb Esteban Lorenzano <[hidden email]>:

> yes, that's because I failed to configure the new fonts and system fallbacks to the default font... to everything.
> anyway I switched back, while I see why font changes are not taken into account.
>
> no log needed :)
>
> On Oct 17, 2013, at 7:53 PM, [hidden email] wrote:
>
>> Not sure if anyone noticed this previously, but I had a problem with Monticello repositories not showing the usual convention to bold and underline items to indicate which were in the image - and tracked this down to being introduced between builds #30469 and #30470.  Coincidently this is where the default font seemed to change from DejaVu to Source Code Pro.  Looks like the default is back to DejaVi in build #30497, so I'm not sure what you'd like to do about logging this as an issue.
>>
>> cheers -ben
>>
>
>


Reply | Threaded
Open this post in threaded view
|

Re: default monospaced code font

Nicolas Cellier
Yeah, there are subjects for which every one can have a cheap and strong opinion.
It's not like discussing the arcane of OldCompiler, gory Morphic layout details, or whatever..
Every one wanting to improve this area is now aware of skinny reactions :)


2013/10/18 Norbert Hartl <[hidden email]>
97 (..well…98) mails in one thread is quite a number. So fonts seems to be the biggest concern these days. That could say something about pharo ;)

Norbert
Am 17.10.2013 um 19:58 schrieb Esteban Lorenzano <[hidden email]>:

> yes, that's because I failed to configure the new fonts and system fallbacks to the default font... to everything.
> anyway I switched back, while I see why font changes are not taken into account.
>
> no log needed :)
>
> On Oct 17, 2013, at 7:53 PM, [hidden email] wrote:
>
>> Not sure if anyone noticed this previously, but I had a problem with Monticello repositories not showing the usual convention to bold and underline items to indicate which were in the image - and tracked this down to being introduced between builds #30469 and #30470.  Coincidently this is where the default font seemed to change from DejaVu to Source Code Pro.  Looks like the default is back to DejaVi in build #30497, so I'm not sure what you'd like to do about logging this as an issue.
>>
>> cheers -ben
>>
>
>



Reply | Threaded
Open this post in threaded view
|

Re: default monospaced code font

Frank Shearar-3
That's why we call it a bikeshed: if you ask for opinions on something
deeply arcane (nuclear reactor plans, compilers, ...) you get no
reaction because the investment needed to actually comment properly is
just too high. But everyone knows how to build a bikeshed, so everyone
fights over the colour!

frank

On 18 October 2013 11:57, Nicolas Cellier
<[hidden email]> wrote:

> Yeah, there are subjects for which every one can have a cheap and strong
> opinion.
> It's not like discussing the arcane of OldCompiler, gory Morphic layout
> details, or whatever..
> Every one wanting to improve this area is now aware of skinny reactions :)
>
>
> 2013/10/18 Norbert Hartl <[hidden email]>
>>
>> 97 (..well…98) mails in one thread is quite a number. So fonts seems to be
>> the biggest concern these days. That could say something about pharo ;)
>>
>> Norbert
>> Am 17.10.2013 um 19:58 schrieb Esteban Lorenzano <[hidden email]>:
>>
>> > yes, that's because I failed to configure the new fonts and system
>> > fallbacks to the default font... to everything.
>> > anyway I switched back, while I see why font changes are not taken into
>> > account.
>> >
>> > no log needed :)
>> >
>> > On Oct 17, 2013, at 7:53 PM, [hidden email] wrote:
>> >
>> >> Not sure if anyone noticed this previously, but I had a problem with
>> >> Monticello repositories not showing the usual convention to bold and
>> >> underline items to indicate which were in the image - and tracked this down
>> >> to being introduced between builds #30469 and #30470.  Coincidently this is
>> >> where the default font seemed to change from DejaVu to Source Code Pro.
>> >> Looks like the default is back to DejaVi in build #30497, so I'm not sure
>> >> what you'd like to do about logging this as an issue.
>> >>
>> >> cheers -ben
>> >>
>> >
>> >
>>
>>
>

Reply | Threaded
Open this post in threaded view
|

Re: default monospaced code font

Igor Stasenko


On 18 October 2013 13:00, Frank Shearar <[hidden email]> wrote:
That's why we call it a bikeshed: if you ask for opinions on something
deeply arcane (nuclear reactor plans, compilers, ...) you get no
reaction because the investment needed to actually comment properly is
just too high. But everyone knows how to build a bikeshed, so everyone
fights over the colour!

 
Hell, yeah. Nevertheless it is important.
As in real life, we all like when we are surrounded by beautiful and useful stuff.
Sometimes beauty prevails usefulness, sometimes opposite,
but it always two key factors which we consider when acquiring new stuff,
and they almost never come alone.
 
I think it comes from subconscious assumption that perfection has a physical form,
which you can be able perceive with naked eye :)

 
frank

On 18 October 2013 11:57, Nicolas Cellier
<[hidden email]> wrote:
> Yeah, there are subjects for which every one can have a cheap and strong
> opinion.
> It's not like discussing the arcane of OldCompiler, gory Morphic layout
> details, or whatever..
> Every one wanting to improve this area is now aware of skinny reactions :)
>
>
> 2013/10/18 Norbert Hartl <[hidden email]>
>>
>> 97 (..well…98) mails in one thread is quite a number. So fonts seems to be
>> the biggest concern these days. That could say something about pharo ;)
>>
>> Norbert
>> Am 17.10.2013 um 19:58 schrieb Esteban Lorenzano <[hidden email]>:
>>
>> > yes, that's because I failed to configure the new fonts and system
>> > fallbacks to the default font... to everything.
>> > anyway I switched back, while I see why font changes are not taken into
>> > account.
>> >
>> > no log needed :)
>> >
>> > On Oct 17, 2013, at 7:53 PM, [hidden email] wrote:
>> >
>> >> Not sure if anyone noticed this previously, but I had a problem with
>> >> Monticello repositories not showing the usual convention to bold and
>> >> underline items to indicate which were in the image - and tracked this down
>> >> to being introduced between builds #30469 and #30470.  Coincidently this is
>> >> where the default font seemed to change from DejaVu to Source Code Pro.
>> >> Looks like the default is back to DejaVi in build #30497, so I'm not sure
>> >> what you'd like to do about logging this as an issue.
>> >>
>> >> cheers -ben
>> >>
>> >
>> >
>>
>>
>




--
Best regards,
Igor Stasenko.
1 ... 3456