On 3 February 2016 at 22:56, Mike Hodnick <email obscured>> wrote:
> Yes, when highlighted, these three lines do NOT work in Atom:
>
> d1 $ sound "x"
>
> d2 $ sound "y"
>
> Just for clarification's sake, in my usage of Atom I never highlight lines.
> It will execute an entire region of code when your cursor is inside that
> region. A region is considered lines of code with no blank lines. e.g. if
> my cursor is on line #2 of the code below, it will only execute the "d1"
> code (no selection required) when eval'ing with the Ctrl+Enter command:
>
>
>
>
> On Wed, Feb 3, 2016 at 4:39 PM, Ogborn, David <email obscured>> wrote:
>
>> Ok, that’s what I would have expected from what you show there. When the
>> two lines are both sent within the same :{ :} block, Haskell attempts to
>> evaluate them as a single expression and they aren’t one, so it doesn’t
>> work.
>>
>> And I guess, just to confirm, this _also_ doesn’t work in Atom, right?
>>
>> d1 $ sound “x”
>>
>> d2 $ sound “y”
>> (with the three lines above all highlighted and evaluated together)
>>
>> Yours truly,
>> David
>>
>> > On Feb 3, 2016, at 1:55 PM, Mike Hodnick <email obscured>> wrote:
>> >
>> > this does NOT work in Atom (when evaluating a whole block):
>> >
>> > d1 $ sound "x"
>> > d2 $ sound "y"
>> >
>> > I don't know coffeescript and Atom packages very well, but this is how
>> the
>> > tidal-atom package handles eval'ing a whole block (where multiple blocks
>> > are separated by a blank line):
>> >
>> > //https://github.com/seansay/atom-tidal/blob/master/lib/repl.coffee
>> > tidalSendExpression: (expression) ->
>> > @tidalSendLine(':{')
>> > (@tidalSendLine(e) for e in expression.split('\n'))
>> > @tidalSendLine(':}')
>> >
>> >
>> >
>> >
>> >
>> > On Wed, Feb 3, 2016 at 12:38 PM, Ogborn, David <email obscured>>
>> wrote:
>> >
>> >> Does this work in Atom/Emacs though?
>> >> d1 $ sound “bd”
>> >> d2 $ sound “cp”
>> >> (all evaluated at the same time, not separately)
>> >>
>> >> Because if this works:
>> >> d1 $ sound “bd”
>> >> |+| speed “2”
>> >>
>> >> i.e. without indentation, then that suggests to me that the newline at
>> the
>> >> end of the first line is being knocked and replaced with whitespace or
>> >> something like that…
>> >>
>> >> (I don’t have a working Emacs/Atom Tidal setup at the moment, by the
>> way…
>> >> I should really reinstall that!)
>> >>
>> >> -D
>> >>
>> >>> On Feb 3, 2016, at 1:21 PM, Mike Hodnick <email obscured>>
>> wrote:
>> >>>
>> >>> OK, that all makes sense. The new lines _without_ a leading space do
>> work
>> >>> in Atom. I believe it works in Emacs as well.
>> >>>
>> >>> -Mike
>> >>>
>> >>>
>> >>> On Wed, Feb 3, 2016 at 12:14 PM, Ogborn, David <email obscured>>
>> >> wrote:
>> >>>
>> >>>>
>> >>>>
>> >>>> Our emails crossed!
>> >>>>
>> >>>> Does this work in other Tidal environments?:
>> >>>> d1 $ sound “test”
>> >>>> | | speed “2”
>> >>>>
>> >>>> Apart from the specific question here, I think it’s a good idea to
>> have
>> >>>> different selectable “sanitizer” functions for different contexts.
>> >>>> Ultimately these might best be placed in the browser-side so that
>> >>>> individual users in a collaborative situation
>> >>>> can control the sanitizer that makes most sense for how they are
>> >>>> currently working in a given block. There’s an extra complexity there
>> >>>> because the sanitizer selections will have to be shared via the
>> >> operational
>> >>>> transform library just like the code editing
>> >>>> operations… so in the short term just making universal sanitizers
>> >>>> selectable in the node.js “client” would be easier to implement.
>> >>>>
>> >>>> (Short answer I should have said first anyway: implement away! Maybe
>> >> fork
>> >>>> on github, create a branch, and then work from there?)
>> >>>>
>> >>>> Yours truly,
>> >>>> David
>> >>>>
>> >>>> On Feb 3, 2016, at 1:01 PM, Mike Hodnick <email obscured>
>> >> <mailto:
>> >>>> <email obscured>> wrote:
>> >>>>
>> >>>> I
>> >>>> forgot to mention that I realize that additional lines in a Tidal
>> block
>> >>>> can
>> >>>> be specified with a leading space or tab. I'm just hoping to avoid
>> this
>> >>>> extra
>> >>>> character though.
>> >>>>
>> >>>> -Mike
>> >>>>
>> >>>> On
>> >>>> Wed, Feb 3, 2016 at 11:56 AM, Mike Hodnick <email obscured>
>> >>>> <email obscured>>
>> >>>> wrote:
>> >>>>
>> >>>> Has there been any attempt to allow new lines within a block of Tidal
>> >> code
>> >>>> in Extramuros? I'm looking at the sanitizeStringForTidal function...
>> it
>> >>>> looks like it would be very possible to do this but I wanted to check
>> >> with
>> >>>> the forum here first to see if there were any thoughts on doing this.
>> >>>> Basically, I want to allow this to be typed in one box:
>> >>>> --- start --- d1 $ sound test | | speed 2 --- end ---
>> >>>> This currently is not allowed in Extramuros. Instead, the code has to
>> be
>> >>>> written like this:
>> >>>> --- start --- d1 $ sound test | | speed 2 --- end ---
>> >>>> As I understand the current code, the reason for this is so that
>> >> separate
>> >>>> dirt connections can be used in the same text box:
>> >>>> --- start --- d1 $ sound test | | speed 2
>> >>>> d2 $ sound also a test | | speed 1 2 3 --- end ---
>> >>>> Ideally, I'd like to do this:
>> >>>> --- start --- d1 $ sound test | | speed 2
>> >>>> d2 $ sound also a test | | speed 1 2 3 --- end ---
>> >>>> I think this is doable and would love to implement this. Thoughts?
>> >>>> -Mike
>> >>>>
>> >>>> --
>> >>>>
>> >>>> Read
>> >>>> the whole topic here: extramuros:
>> >>>> http://lurk.org/r/topic/3O3uTAr1kZMLyrZKvLYgzI <
>> >>>> http://lurk.org/r/topic/3O3uTAr1kZMLyrZKvLYgzI>
>> >>>>
>> >>>> To
>> >>>> leave extramuros, email <email obscured> <mailto:
>> >>>> <email obscured>> with
>> >>>> the following email subject: unsubscribe
>> >>>>
>> >>>>
>> >>>> --
>> >>>>
>> >>>> Read the whole topic here: extramuros:
>> >>>> http://lurk.org/r/topic/4DgmjaQlR3MMIAeMRE9yh8
>> >>>>
>> >>>> To leave extramuros, email <email obscured> with the
>> following
>> >>>> email subject: unsubscribe
>> >>>>
>> >>>
>> >>> --
>> >>>
>> >>> Read the whole topic here: extramuros:
>> >>> http://lurk.org/r/topic/74yyDdejdwxRLLnzGC4VwW
>> >>>
>> >>> To leave extramuros, email <email obscured> with the
>> following
>> >> email subject: unsubscribe
>> >>
>> >>
>> >> --
>> >>
>> >> Read the whole topic here: extramuros:
>> >> http://lurk.org/r/topic/3plcZNwEMg7Zh8hhkvnrpr
>> >>
>> >> To leave extramuros, email <email obscured> with the following
>> >> email subject: unsubscribe
>> >>
>> >
>> > --
>> >
>> > Read the whole topic here: extramuros:
>> > http://lurk.org/r/topic/r8EIA8Jriv8i1R2Ge3S1O
>> >
>> > To leave extramuros, email <email obscured> with the following
>> email subject: unsubscribe
>>
>>
>> --
>>
>> Read the whole topic here: extramuros:
>> http://lurk.org/r/topic/jo89pykRARd8vxgCc4W1g
>>
>> To leave extramuros, email <email obscured> with the following
>> email subject: unsubscribe
>>
>
> --
>
> Read the whole topic here: extramuros:
> http://lurk.org/r/topic/4b78Xn1j87dpeuCdpgYohI
>
> To leave extramuros, email <email obscured> with the following email
subject: unsubscribe
--
http://yaxu.org/