I think there is a consensus we need to keep #cr and #lf as intended, yet to
add some kind of #newLine (which btw is different to EOL :P) vocabulary, isn’t?
In this, I favour Peter approach for define line ending convention (the way
#newLine will work)… and of course by default it should use the
On Sat, Aug 05, 2017 at 10:49:02AM +0200, Esteban Lorenzano wrote:
> I think there is a consensus we need to keep #cr and #lf as intended,
> yet to add some kind of #newLine (which btw is different to EOL :P)
> vocabulary, isn???t?
>
> In this, I favour Peter approach for define line ending conven
> On 5 Aug 2017, at 11:06, Alistair Grant wrote:
>
> On Sat, Aug 05, 2017 at 10:49:02AM +0200, Esteban Lorenzano wrote:
>> I think there is a consensus we need to keep #cr and #lf as intended,
>> yet to add some kind of #newLine (which btw is different to EOL :P)
>> vocabulary, isn???t?
>>
>> I
On Sat, Aug 05, 2017 at 11:09:51AM +0200, Esteban Lorenzano wrote:
>
> > On 5 Aug 2017, at 11:06, Alistair Grant wrote:
> >
> > On Sat, Aug 05, 2017 at 10:49:02AM +0200, Esteban Lorenzano wrote:
> >> I think there is a consensus we need to keep #cr and #lf as intended,
> >> yet to add some kind
> On 5 Aug 2017, at 11:14, Alistair Grant wrote:
>
> On Sat, Aug 05, 2017 at 11:09:51AM +0200, Esteban Lorenzano wrote:
>>
>>> On 5 Aug 2017, at 11:06, Alistair Grant wrote:
>>>
>>> On Sat, Aug 05, 2017 at 10:49:02AM +0200, Esteban Lorenzano wrote:
I think there is a consensus we need to
> I think there is a consensus we need to keep #cr and #lf as intended
Is there?
My argument was that there's no (obvious) reason to combine different line
endings in the same document. Therefore if you were to use #cr, #lf, #crlf, you
would actually mean that you just want to enter newline.
S
> On 5 Aug 2017, at 11:17, Peter Uhnak wrote:
>
>> I think there is a consensus we need to keep #cr and #lf as intended
>
> Is there?
>
> My argument was that there's no (obvious) reason to combine different line
> endings in the same document. Therefore if you were to use #cr, #lf, #crlf,
>
Hi Esteban,
On Sat, Aug 05, 2017 at 11:30:58AM +0200, Esteban Lorenzano wrote:
>
> > On 5 Aug 2017, at 11:17, Peter Uhnak wrote:
> >
> >> I think there is a consensus we need to keep #cr and #lf as intended
> >
> > Is there?
> >
> > My argument was that there's no (obvious) reason to combine
This is gorgeous!
Alexandre
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
> On Aug 4, 2017, at 6:19 PM, Tudor Girba wrote:
>
> Hi,
>
> We are very happy to announce the alpha version of a moldab
+1
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
> On Aug 4, 2017, at 8:19 AM, Esteban Lorenzano wrote:
>
> sometimes you actually want to write a cr (or a lf). So it needs to remain in
> the syst
On Friday 04 August 2017 07:11 PM, Damien Pollet wrote:
Stream >> newLineFor: platform
self nextPutAll: platform lineEnding
EOL encoding is a property of a text file and not a platform. While
files created on a certain proprietary platforms ;-) may use an encoding
that does not make it
It seems to be very snappy considering the size of the file and its amount
of characters.
I still don't get how Bloc and Brick plays in current Pharo, nor what this
"moldability" adds to it.
But performancewise it seems to be an improvement over the existing editor
(Rubric?).
Congratulations!
So one step at a time:
- #cr and #lf just put this character in the stream.
- #newLine put the underlying OS line ending. ( and sorry for the
nostalgic but nl sucks and to me this is netherlands and not newline
:).
Then we should revisit all the cr inside the system and use newline.
Then we shoul
Hi torsten
Yes it sounds good to have MAJOR.MINOR.PATCH/BUILDNUMBER scheme
On Fri, Aug 4, 2017 at 9:22 AM, Torsten Bergmann wrote:
> Hi Ben,
>
> reason is that for Pharo 7 currently an sha git hash is used in the file
> name
> instead of a (more clear) build number.
>
> See http://files.pharo.or
Hi guys
I would like to know if there is a pattern to build extensible menu in Spec.
For example, I extending Epicea to support pillar fileout so that I
can turn a coding section into a pillar steps of action.
I wanted to extend the epicea browser to get my menu in:
But the code is like that:
EP
On Sat, Aug 5, 2017 at 6:14 PM, Stephane Ducasse
wrote:
> So one step at a time:
>
> - #cr and #lf just put this character in the stream.
> - #newLine put the underlying OS line ending. ( and sorry for the
> nostalgic but nl sucks and to me this is netherlands and not newline
> :).
>
> Then we sho
:)
Me too.
Stef
On Sat, Aug 5, 2017 at 6:32 PM, Cyril Ferlicot wrote:
> On Sat, Aug 5, 2017 at 6:14 PM, Stephane Ducasse
> wrote:
>> So one step at a time:
>>
>> - #cr and #lf just put this character in the stream.
>> - #newLine put the underlying OS line ending. ( and sorry for the
>> nostalgi
Hi Stef,
On 5 August 2017 at 18:14, Stephane Ducasse wrote:
> So one step at a time:
>
> - #cr and #lf just put this character in the stream.
> - #newLine put the underlying OS line ending. ( and sorry for the
> nostalgic but nl sucks and to me this is netherlands and not newline
> :).
Beyond th
Hi all,
First, we should not confuse "writing into a stream" with "writing into a
text file". Not all streams are to write into a text file. This means that
we cannot pretend that the basic stream implementation should always do a
conversion. I think that should belong to a text writer, also manag
Hi,
just to (hopefully) clarify my intention, maybe pseudocode would describe my
thoughts better.
Stream>>beForWindows
"Use consistenly Windows line endings (CRLF) in the stream"
self convertLineEndings: true
lineEnding := String crlf
Stream>>convertLineEndings: aBoolean
Hi Stef,
I faced similar issue and then I've found out that PragmaMenuBuilder is
compatible with Spec.
Something like...
builder := PragmaMenuBuilder pragmaKeyword: 'myPragma' model: self.
menu := MenuModel new.
menu fromSpec: builder menuSpec.
Peter
On Sat, Aug 05, 2017 at 06:26:45PM +0200,
21 matches
Mail list logo
