Smalltalk › Squeak › Squeak - Dev

Is it just me or is class comment editing totally broken in 4.5?

_‹ Previous Topic Next Topic _›

Classic

List

Threaded

37 messages Options

David T. Lewis

Is it just me or is class comment editing totally broken in 4.5?

Create a new class, attempt to edit the class comment ==> Error: RemoteString past end of file

Surely I cannot be the first person to have edited a class comment in the last month or so ... I hope.

Dave

David T. Lewis

How do I convince a Workspace to stop "helping" me?

Whenever I type an open-paren $( in a Squeak 4.5 workspace, some mysterious
agent of code format rectitude steps in and supplies the matching close-paren.
This is hugely annoying and I can't seem to find any preferences or workspace
menu settings to make it stop.

Does anyone know how to make this feature go away?

Dave

timrowledge

Re: How do I convince a Workspace to stop "helping" me?

On 09-04-2014, at 5:11 PM, David T. Lewis <[hidden email]> wrote:

> Whenever I type an open-paren $( in a Squeak 4.5 workspace, some mysterious
> agent of code format rectitude steps in and supplies the matching close-paren.
> This is hugely annoying and I can't seem to find any preferences or workspace
> menu settings to make it stop.
>
> Does anyone know how to make this feature go away?

Helpful code can be so unhelpful, right? See if by any chance the syntaxHighlightinasyoutype preference is on - in the ‘browsing’ section of the prefs browser. There’s also shoutstylinginworkspace. Neither of them was on in my 4.5 image but y’never know.

tim
--
tim Rowledge; [hidden email]; http://www.rowledge.org/tim
Strange OpCodes: XYZZY: Branch and Play Adventure

David T. Lewis

Re: How do I convince a Workspace to stop "helping" me?

On Wed, Apr 09, 2014 at 05:18:27PM -0700, tim Rowledge wrote:

>
> On 09-04-2014, at 5:11 PM, David T. Lewis <[hidden email]> wrote:
>
> > Whenever I type an open-paren $( in a Squeak 4.5 workspace, some mysterious
> > agent of code format rectitude steps in and supplies the matching close-paren.
> > This is hugely annoying and I can't seem to find any preferences or workspace
> > menu settings to make it stop.
> >
> > Does anyone know how to make this feature go away?
>
> Helpful code can be so unhelpful, right? See if by any chance the syntaxHighlightinasyoutype preference is on - in the ?browsing? section of the prefs browser. There?s also shoutstylinginworkspace. Neither of them was on in my 4.5 image but y?never know.
>

I tried both of those, no joy. Actually, I looked through every preference
in the Preference Browser, and all the settings in the workspace menu. I must
be missing something, but I can't make this feature go away.

Dave

Colin Putney-3

Re: How do I convince a Workspace to stop "helping" me?

On Wed, Apr 9, 2014 at 7:37 PM, David T. Lewis <[hidden email]> wrote:

I tried both of those, no joy. Actually, I looked through every preference
in the Preference Browser, and all the settings in the workspace menu. I must
be missing something, but I can't make this feature go away.

You want the "Auto Enclose" preference in category "Morphic".

I can't stand it either. Surprisingly little of my coding consists of typing code out linearly.

timrowledge

Re: How do I convince a Workspace to stop "helping" me?

On 09-04-2014, at 5:54 PM, Colin Putney <[hidden email]> wrote:

>
>
>
> On Wed, Apr 9, 2014 at 7:37 PM, David T. Lewis <[hidden email]> wrote:
>
> I tried both of those, no joy. Actually, I looked through every preference
> in the Preference Browser, and all the settings in the workspace menu. I must
> be missing something, but I can't make this feature go away.
>
> You want the "Auto Enclose" preference in category "Morphic".
>
> I can't stand it either. Surprisingly little of my coding consists of typing code out linearly.

Likewise. I really, really, hate this supposedly ‘helpful’ kind of thing.

tim
--
tim Rowledge; [hidden email]; http://www.rowledge.org/tim
A bug in the code is worth two in the documentation.

Chris Muller-3

Re: Is it just me or is class comment editing totally broken in 4.5?

In reply to this post by David T. Lewis

I got that the other day, but I think it was when I was playing around
with condenseSources and condenseChanges. After re-unzipping from the
zip, changing class comment worked for me.

On Wed, Apr 9, 2014 at 6:52 PM, David T. Lewis <[hidden email]> wrote:
> Create a new class, attempt to edit the class comment ==> Error: RemoteString past end of file
>
> Surely I cannot be the first person to have edited a class comment in the last month or so ... I hope.
>
> Dave
>

Ken G. Brown

Re: How do I convince a Workspace to stop "helping" me?

In reply to this post by David T. Lewis

I believe way back in about early 4.4, i was able to do the following in order to get that functionality, I sorta got used to the auto add of the closing bracket.

From my migration script:

"=================================="
"OCompletion provides source code completion as you type"
"Has some issues loading into 10759"
"(Installer ss project: 'OCompletion') install: 'Ocompletion'.
(Smalltalk at: #ECToolSet) register.
(Smalltalk at: #ToolSet) default: (Smalltalk at: #ECToolSet)."

"This is needed in order to reload the saved prefs file"
"Installer ss project: 'MetacelloRepository'; install:
'ConfigurationOfOCompletion'.
#(project stableVersion load)
inject: (Smalltalk at: #ConfigurationOfOCompletion)
into: [ :object :selector | object perform: selector ]."

"OCompletion provides source code completion as you type"
(Installer ss project: 'OCompletion') install: 'Ocompletion'.
(Smalltalk at: #ECToolSet) register.
(Smalltalk at: #ToolSet) default: (Smalltalk at: #ECToolSet).
"==================================“

I’m sorta remember an eCompletion as well, and maybe also something in OmniBrowser?

Hope this helps.

Ken G. Brown

On Apr 9, 2014, at 18:37, David T. Lewis <[hidden email]> wrote:

> On Wed, Apr 09, 2014 at 05:18:27PM -0700, tim Rowledge wrote:
>>
>> On 09-04-2014, at 5:11 PM, David T. Lewis <[hidden email]> wrote:
>>
>>> Whenever I type an open-paren $( in a Squeak 4.5 workspace, some mysterious
>>> agent of code format rectitude steps in and supplies the matching close-paren.
>>> This is hugely annoying and I can't seem to find any preferences or workspace
>>> menu settings to make it stop.
>>>
>>> Does anyone know how to make this feature go away?
>>
>> Helpful code can be so unhelpful, right? See if by any chance the syntaxHighlightinasyoutype preference is on - in the ?browsing? section of the prefs browser. There?s also shoutstylinginworkspace. Neither of them was on in my 4.5 image but y?never know.
>>
>
> I tried both of those, no joy. Actually, I looked through every preference
> in the Preference Browser, and all the settings in the workspace menu. I must
> be missing something, but I can't make this feature go away.
>
> Dave
>

Chris Muller-3

Re: How do I convince a Workspace to stop "helping" me?

In reply to this post by timrowledge

Bonk! Of course, I _love_ Auto Enclose! :-)

Because I'm not "typing a stream of code", I'm "composing nested expressions".

Now, when it included the less-than sign, I resented it, because it
assuemed I was typing HTML. But for '"([ and {, they always go in
pairs. The machine keeps my nestings correct and I can simply
right-arrow to the next outer-level and press Command+Space to expose
and "work on" that expression. Love it.

Of the curiously strongly negative reactions, though, I was able to
glean just one tidbit of feedback (Colins).

On Wed, Apr 9, 2014 at 7:57 PM, tim Rowledge <[hidden email]> wrote:

>
> On 09-04-2014, at 5:54 PM, Colin Putney <[hidden email]> wrote:
>
>>
>>
>>
>> On Wed, Apr 9, 2014 at 7:37 PM, David T. Lewis <[hidden email]> wrote:
>>
>> I tried both of those, no joy. Actually, I looked through every preference
>> in the Preference Browser, and all the settings in the workspace menu. I must
>> be missing something, but I can't make this feature go away.
>>
>> You want the "Auto Enclose" preference in category "Morphic".
>>
>> I can't stand it either. Surprisingly little of my coding consists of typing code out linearly.
>
> Likewise. I really, really, hate this supposedly ‘helpful’ kind of thing.
>
> tim
> --
> tim Rowledge; [hidden email]; http://www.rowledge.org/tim
> A bug in the code is worth two in the documentation.
>
>
>

David T. Lewis

Re: How do I convince a Workspace to stop "helping" me?

In reply to this post by Colin Putney-3

On Wed, Apr 09, 2014 at 07:54:35PM -0500, Colin Putney wrote:

> On Wed, Apr 9, 2014 at 7:37 PM, David T. Lewis <[hidden email]> wrote:
>
>
> > I tried both of those, no joy. Actually, I looked through every preference
> > in the Preference Browser, and all the settings in the workspace menu. I
> > must
> > be missing something, but I can't make this feature go away.
> >
>
> You want the "Auto Enclose" preference in category "Morphic".

Thank you, thank you! That was the problem.

Somehow it never occurred to me that this feature would be related to Morphic,
possibly because it isn't. But the feature is not implemented in MVC, so I
guess that makes it a Morphic preference ;-)

>
> I can't stand it either. Surprisingly little of my coding consists of
> typing code out linearly.

I also find it quite interesting to see how much attention is paid to "making
coding more productive," as if entering more words per minute into code panes
would somehow relate in any positive way to productivity.

Dave

David T. Lewis

Re: How do I convince a Workspace to stop "helping" me?

In reply to this post by Chris Muller-3

On Wed, Apr 09, 2014 at 08:19:37PM -0500, Chris Muller wrote:
> Bonk! Of course, I _love_ Auto Enclose! :-)
>
> Because I'm not "typing a stream of code", I'm "composing nested expressions".

Ha! It makes sense to me now that you explain it that way. I guess that's why it's a preference :-)

For myself, much of what I do in workspaces has little to do with writing
code, which is why it comes across to me as an annoyance.

Dave

>
> Now, when it included the less-than sign, I resented it, because it
> assuemed I was typing HTML. But for '"([ and {, they always go in
> pairs. The machine keeps my nestings correct and I can simply
> right-arrow to the next outer-level and press Command+Space to expose
> and "work on" that expression. Love it.
>
> Of the curiously strongly negative reactions, though, I was able to
> glean just one tidbit of feedback (Colins).
>
> On Wed, Apr 9, 2014 at 7:57 PM, tim Rowledge <[hidden email]> wrote:
> >
> > On 09-04-2014, at 5:54 PM, Colin Putney <[hidden email]> wrote:
> >
> >>
> >>
> >>
> >> On Wed, Apr 9, 2014 at 7:37 PM, David T. Lewis <[hidden email]> wrote:
> >>
> >> I tried both of those, no joy. Actually, I looked through every preference
> >> in the Preference Browser, and all the settings in the workspace menu. I must
> >> be missing something, but I can't make this feature go away.
> >>
> >> You want the "Auto Enclose" preference in category "Morphic".
> >>
> >> I can't stand it either. Surprisingly little of my coding consists of typing code out linearly.
> >
> > Likewise. I really, really, hate this supposedly ???helpful??? kind of thing.
> >
> > tim
> > --
> > tim Rowledge; [hidden email]; http://www.rowledge.org/tim
> > A bug in the code is worth two in the documentation.
> >
> >
> >

Frank Shearar-3

Re: How do I convince a Workspace to stop "helping" me?

In reply to this post by Chris Muller-3

On 10 April 2014 02:19, Chris Muller <[hidden email]> wrote:
> Bonk! Of course, I _love_ Auto Enclose! :-)
>
> Because I'm not "typing a stream of code", I'm "composing nested expressions".

Hey, for a change I agree with Chris! For any Lisp users out there,
the equivalent is a paredit-mode lite. Paredit (an Emacs mode) is all
about composing and manipulating nested expressions. What would make
auto-enclose much more paredit like is automating the manipulation of
parens. Not just adding a ) every time you type a ( but letting e you
"slurp" expressions into the enclosing paren (whether [], {} or ()
parens) or "burp" them out, deleting empty pairs of parens, and so on.
Paredit takes a bit of getting used to - precisely because you're
leaning on the IDE more to manipulate expressions rather than
adding/deleting characters - but once you get used to it, it's
awesome.

frank

Herbert König

Re: Is it just me or is class comment editing totally broken in 4.5?

In reply to this post by David T. Lewis

Hi,

works for me in two images on two OS.

Cheers,

Herbert

Am 10.04.2014 01:52, schrieb David T. Lewis:
> Create a new class, attempt to edit the class comment ==> Error: RemoteString past end of file
>
> Surely I cannot be the first person to have edited a class comment in the last month or so ... I hope.
>
> Dave
>

tty

Re: Is it just me or is class comment editing totally broken in 4.5?

In reply to this post by David T. Lewis

WriteStream>>nextChunkPut

add a self flush at the end will fix it.

Discussion several months ago fingered the gcc 4 compiler so something.

cheers.

tty

---- On Wed, 09 Apr 2014 16:52:54 -0700 David T. Lewis<[hidden email]> wrote ----

Create a new class, attempt to edit the class comment ==> Error: RemoteString past end of file

Surely I cannot be the first person to have edited a class comment in the last month or so ... I hope.

Dave

tty

Re: How do I convince a Workspace to stop "helping" me?

In reply to this post by Frank Shearar-3

>...Not just adding a ) every time you type a ( but letting e you
>"slurp" expressions into the enclosing paren (whether [], {} or ()

>parens) or "burp" them out, deleting empty pairs of parens, and so on.

Throw in a few microwave burritos and coding smalltalk will sound downright symphonic.

Herbert König

Re: How do I convince a Workspace to stop "helping" me?

In reply to this post by Frank Shearar-3

Having worked in AutoLisp for quite some times I heavily used this
feature. Enclose parts of expressions when I got precedence wrong or to
temporarily commenting out code with this feature was really handy.

It's been nasty with < and with ' in comments.

So when it was gone and I didn't find the preference I just stopped
using the feature :-))

Cheers

Herbert

Am 10.04.2014 11:47, schrieb Frank Shearar:

> On 10 April 2014 02:19, Chris Muller <[hidden email]> wrote:
>> Bonk! Of course, I _love_ Auto Enclose! :-)
>>
>> Because I'm not "typing a stream of code", I'm "composing nested expressions".
> Hey, for a change I agree with Chris! For any Lisp users out there,
> the equivalent is a paredit-mode lite. Paredit (an Emacs mode) is all
> about composing and manipulating nested expressions. What would make
> auto-enclose much more paredit like is automating the manipulation of
> parens. Not just adding a ) every time you type a ( but letting e you
> "slurp" expressions into the enclosing paren (whether [], {} or ()
> parens) or "burp" them out, deleting empty pairs of parens, and so on.
> Paredit takes a bit of getting used to - precisely because you're
> leaning on the IDE more to manipulate expressions rather than
> adding/deleting characters - but once you get used to it, it's
> awesome.
>
> frank
>

Alejandro F. Reimondo

Re: How do I convince a Workspace to stop "helping" me?

In reply to this post by timrowledge

>Likewise. I really, really, hate this supposedly ‘helpful’ kind of thing.

+1
How we can do to promote reading instead of (fast) writing?
...and to delegate/refactor instead of composing expressions/objects.

IMHO, Help while writing is short term help.

Ale.

----- Original Message -----
From: "tim Rowledge" <[hidden email]>
To: "The general-purpose Squeak developers list"
<[hidden email]>
Sent: Wednesday, April 09, 2014 9:57 PM
Subject: Re: [squeak-dev] How do I convince a Workspace to stop "helping"
me?

On 09-04-2014, at 5:54 PM, Colin Putney <[hidden email]> wrote:

>
>
>
> On Wed, Apr 9, 2014 at 7:37 PM, David T. Lewis <[hidden email]>
> wrote:
>
> I tried both of those, no joy. Actually, I looked through every preference
> in the Preference Browser, and all the settings in the workspace menu. I
> must
> be missing something, but I can't make this feature go away.
>
> You want the "Auto Enclose" preference in category "Morphic".
>
> I can't stand it either. Surprisingly little of my coding consists of
> typing code out linearly.

Likewise. I really, really, hate this supposedly ‘helpful’ kind of thing.

tim
--
tim Rowledge; [hidden email]; http://www.rowledge.org/tim
A bug in the code is worth two in the documentation.

David T. Lewis

Re: Is it just me or is class comment editing totallyÂ Â Â Â broken in 4.5?

In reply to this post by tty

Ah, right, thank you! I do recall the discussion now that you mention it.
I use VMs compiled on my own machine, which happens to be a new Ubuntu
system at the moment. It probably has the buggy gcc library.

Thanks a lot,
Dave

> WriteStream>>nextChunkPut
>
>
>
> add a self flush at the end will fix it.
>
>
>
>
> Discussion several months ago fingered the gcc 4 compiler so something.
>
>
>
>
>
>
>
>
>
>
> cheers.
>
>
> tty
>
> ---- On Wed, 09 Apr 2014 16:52:54 -0700 David T.
> Lewis<[hidden email]> wrote ----
>
>
> Create a new class, attempt to edit the class comment ==> Error:
> RemoteString past end of file
>
> Surely I cannot be the first person to have edited a class comment in the
> last month or so ... I hope.
>
> Dave
>
>
>
>
>

Chris Muller-3

Re: How do I convince a Workspace to stop "helping" me?

In reply to this post by David T. Lewis

Frank wrote:

> What would make
> auto-enclose much more paredit like is automating the manipulation of
> parens. Not just adding a ) every time you type a ( but letting e you
> "slurp" expressions into the enclosing paren (whether [], {} or ()
> parens) or "burp" them out, deleting empty pairs of parens, and so on.

Hey, did you happen to know about Command+', Command+Shift+",
Command+(, Command+[, and Command+Shift+{ ? :-) They let you do
exactly what I think you're saying.

1) Select an expression by either click+drag, double-clicking just
inside any of ', ", (, [, {, }, ], or ), or, if you're at the
keyboard, Command+Space when the text-cursor is positioned there.
Note, the selection does not include the bracket/paren characters
themselves, but up-to just inside them.

2) Press one of the above-mentioned Command key sequences. If you
press the same one that you're already in, it will toggle between
adding/removing that expression ("slurp"). If you press one of those
Command-key sequences that is different than the expression, it will
add that surrounding bracket around the expression, toggling it on and
off ("burp").

- Chris

> Paredit takes a bit of getting used to - precisely because you're
> leaning on the IDE more to manipulate expressions rather than
> adding/deleting characters but once you get used to it, it's
> awesome.

>
> frank
>

Chris Muller-3

Re: How do I convince a Workspace to stop "helping" me?

Oops, for paren its Shift+Command+(, not Command+(.

On Thu, Apr 10, 2014 at 10:11 AM, Chris Muller <[hidden email]> wrote:

> Frank wrote:
>
>> What would make
>> auto-enclose much more paredit like is automating the manipulation of
>> parens. Not just adding a ) every time you type a ( but letting e you
>> "slurp" expressions into the enclosing paren (whether [], {} or ()
>> parens) or "burp" them out, deleting empty pairs of parens, and so on.
>
> Hey, did you happen to know about Command+', Command+Shift+",
> Command+(, Command+[, and Command+Shift+{ ? :-) They let you do
> exactly what I think you're saying.
>
> 1) Select an expression by either click+drag, double-clicking just
> inside any of ', ", (, [, {, }, ], or ), or, if you're at the
> keyboard, Command+Space when the text-cursor is positioned there.
> Note, the selection does not include the bracket/paren characters
> themselves, but up-to just inside them.
>
> 2) Press one of the above-mentioned Command key sequences. If you
> press the same one that you're already in, it will toggle between
> adding/removing that expression ("slurp"). If you press one of those
> Command-key sequences that is different than the expression, it will
> add that surrounding bracket around the expression, toggling it on and
> off ("burp").
>
> - Chris
>
>> Paredit takes a bit of getting used to - precisely because you're
>> leaning on the IDE more to manipulate expressions rather than
>> adding/deleting characters but once you get used to it, it's
>> awesome.
>
>
>
>>
>> frank
>>