TL;DR: AbstractNautilusUI>>buildNewCodeSourceAreaRubric
comment out "withSourceCodeAnnotation;" howto (less than a minute to do): 1. open finder (world > tools > finder) 2. punch in 'Format as you read' and search "source" 3. take a deep breath or two while its searching 4. open found class 4.1. look at hierarchy and try figure out how it's called from Nautilus 4.2. class is not referenced :( … but "class" side is bold so there's something there 4.3. on class side method "key:" returning suspicious selector 4.4. search senders of the selector 5. see who is the sender of the sender 6. profit :) I actually use such approach quite often when trying to figure out UI things and it works surprisingly often. Peter On Fri, Jun 10, 2016 at 7:28 PM, Sven Van Caekenberghe <s...@stfx.eu> wrote: > > > On 10 Jun 2016, at 18:16, PAUL DEBRUICKER <pdebr...@gmail.com> wrote: > > > > Hi - > > > > I don't think I'll be changing the settings for > > > > format as you read > > wrapping > > line number > > > > or reading the cursor position/line number ever. > > > > Is there a way to remove that section from the nautilus code pane? > > I would love to have that too - way too much noise. > > BTW, who in his right mind thought it was a good idea to have line numbers > for Pharo code ? > > > Thanks > > > > > > Paul > > > > >
