Smalltalk › Pharo › Pharo Smalltalk Users

Comments not working in Ubuntu 13.04

_‹ Previous Topic Next Topic _›

Classic

List

Threaded

3 messages Options

kmo

Comments not working in Ubuntu 13.04

I've just noticed that class comments have stopped working in Pharo since I upgraded from Xubuntu 12.10 to Xubuntu 13.04.

If I make any change to a comment or add a new comment I get an error in RemoteString - 'RemoteSring past end of file'.

This happens both for Pharo 2.0 images and older Pharo 1.4 images. It happens if I add comments to new classes or to classes where I have previously successfully added comments.

This is where it falls down:

string
    "Answer the receiver's string if remote files are enabled.
    Use a read only copy to avoid syntax errors when accessed via
    multiple processes."

    | theFile |
    (sourceFileNumber == nil or: [(SourceFiles at: sourceFileNumber) == nil]) ifTrue: [^''].
    theFile := (SourceFiles at: sourceFileNumber) readOnlyCopy.
    ^[filePositionHi > theFile size ifTrue: [
        self error: 'RemoteString past end of file' ].
        theFile position: filePositionHi.
        theFile nextChunk] ensure: [theFile close]

Anyone else seen this? Anyone got a solution?

Ken

Camillo Bruni-3

Re: Comments not working in Ubuntu 13.04

This is a known bug, and I thought it was fixed.

Did you update your 2.0 image to the latest version? (maybe that is not possible with this bug being present).
If you do not manage to update your image, can you try with a fresh 2.0 image?

On 2013-06-22, at 14:33, Kenneth Payne <[hidden email]> wrote:

> I've just noticed that class comments have stopped working in Pharo since I
> upgraded from Xubuntu 12.10 to Xubuntu 13.04.
>
> If I make any change to a comment or add a new comment I get an error in
> RemoteString - 'RemoteSring past end of file'.
>
> This happens both for Pharo 2.0 images and older Pharo 1.4 images. It
> happens if I add comments to new classes or to classes where I have
> previously successfully added comments.
>
> This is where it falls down:
>
>
> string
> "Answer the receiver's string if remote files are enabled.
> Use a read only copy to avoid syntax errors when accessed via
> multiple processes."
>
> | theFile |
> (sourceFileNumber == nil or: [(SourceFiles at: sourceFileNumber) ==
> nil]) ifTrue: [^''].
> theFile := (SourceFiles at: sourceFileNumber) readOnlyCopy.
> ^[filePositionHi > theFile size ifTrue: [
> self error: 'RemoteString past end of file' ].
> theFile position: filePositionHi.
> theFile nextChunk] ensure: [theFile close]
>
> Anyone else seen this? Anyone got a solution?
>
> Ken

kmo

Re: Comments not working in Ubuntu 13.04

Thanks. I've just downloaded the latest Pharo 2.0 for Linux. Works OK.

- Ken

On Sat, Jun 22, 2013 at 1:41 PM, Camillo Bruni <[hidden email]> wrote:

This is a known bug, and I thought it was fixed.

Did you update your 2.0 image to the latest version? (maybe that is not possible with this bug being present).
If you do not manage to update your image, can you try with a fresh 2.0 image?

On 2013-06-22, at 14:33, Kenneth Payne <[hidden email]> wrote:

> I've just noticed that class comments have stopped working in Pharo since I
> upgraded from Xubuntu 12.10 to Xubuntu 13.04.
>
> If I make any change to a comment or add a new comment I get an error in
> RemoteString - 'RemoteSring past end of file'.
>
> This happens both for Pharo 2.0 images and older Pharo 1.4 images. It
> happens if I add comments to new classes or to classes where I have
> previously successfully added comments.
>
> This is where it falls down:
>
>
> string
> "Answer the receiver's string if remote files are enabled.
> Use a read only copy to avoid syntax errors when accessed via
> multiple processes."
>
> | theFile |
> (sourceFileNumber == nil or: [(SourceFiles at: sourceFileNumber) ==
> nil]) ifTrue: [^''].
> theFile := (SourceFiles at: sourceFileNumber) readOnlyCopy.
> ^[filePositionHi > theFile size ifTrue: [
> self error: 'RemoteString past end of file' ].
> theFile position: filePositionHi.
> theFile nextChunk] ensure: [theFile close]
>
> Anyone else seen this? Anyone got a solution?
>
> Ken