Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
  • Jan 17 22:22
    hiiamboris opened #208
  • Jan 16 17:26

    dockimbel on 0.6.5

    FEAT: adds extra description fo… (compare)

  • Jan 15 18:41

    dockimbel on 0.6.5

    FIX: missing multiline string! … (compare)

  • Jan 14 11:48
    9214 synchronize #204
  • Jan 13 19:12
    9214 synchronize #204
  • Jan 13 18:34

    dockimbel on 0.6.5

    FEAT: adding a page for documen… (compare)

  • Jan 13 10:51
    hiiamboris commented #204
  • Jan 10 01:27
    9214 synchronize #204
  • Jan 09 13:41
    9214 commented #204
  • Jan 09 12:27
    bubnenkoff commented #204
  • Jan 09 12:27
    bubnenkoff commented #204
  • Jan 07 21:17

    greggirwin on master

    cs/view adoc modified Merge pull request #207 from To… (compare)

  • Jan 07 21:17
    greggirwin closed #207
  • Jan 07 20:54
    9214 edited #206
  • Jan 07 20:48
    9214 commented #195
  • Jan 07 20:06
    Tovim opened #207
  • Jan 07 19:39
    greggirwin commented #205
  • Jan 07 17:57
    9214 commented #205
  • Jan 07 17:46

    greggirwin on master

    FEAT: add entry on calendar face FIX: minor formatting correctio… FIX: reflect changes in calenda… and 1 more (compare)

  • Jan 07 17:46
    greggirwin closed #205
lan Nomar
@khwerz
but red is a strange language, because the code is documented, you don't have a help file which could use another license, also BSD itself licenses the documentation using another license as you can see https://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/legalnotice.html
of course, I might be incredibly confused on the matter, also this is well above my pay grade
you can tell the gpl is a problem, a good example is toybox, which was made as a relicensing of busybox
Gregg Irwin
@greggirwin
We probably need to look at official doc licenses as well, but BSD should be applicable to any media. Should be less confusing than mixing special purpose licenses, if there's not a strong need for them.
VaZub
@vazub
By the way, since you touched the issue of licenses. I have adopted myself and strongly recommend anyone interested to consider using Blue Oak Model License - https://blueoakcouncil.org/2019/03/06/model.html. This is a modern permissive license in vein of BSD, but with an explicit patent grant and, even more important - with its contents written in HUMAN language, instead of typical "legalese". However, it is written by professional lawyers, so the risk of "new and untested" stigma can be remedied to some extent here. And additional fun reason - it is intended to simplify licensing and improve legibility for all parties involved, which seems to align quite smoothly with the reported Red's goal of "REDucing complexity" :)
Gregg Irwin
@greggirwin

Looks interesting. Not being a lawyer, one thing (twice) is not intuitive to my layman's mind. The phrase "would otherwise infringe" is legalese to me. Why not "does not infringe"?

Certainly it's clearer than the big final para in BSD3, but it still has 8 sections. Each has a clear purpose, which is nice.

VaZub
@vazub

@greggirwin

Looks interesting. Not being a lawyer, one thing (twice) is not intuitive to my layman's mind. The phrase "would otherwise infringe" is legalese to me. Why not "does not infringe"?

In case of your suggested wording : "(do everything) ...that does not infringe... (copyright/patent)", makes little sense, because you don't need to give permission to do something that doesn't require such permission in the first place. On the other hand, "(do everything) ...that would otherwise infringe... (copyright/patent)" refers to all applicable effects on the covered items that do require preliminary permission in order to comply. "Otherwise" here means "in case there is no explicit permission/license provided". "Would infringe" refers to the fact, that according Copyright Law, you are violating the copyright by default, if there is no provision by the copyright holder to allow you to do something.

mikeparr
@mikeparr
Hello all, what do you wish me to do?
Gregg Irwin
@greggirwin

Hey @mikeparr!

1) Confirm that BSD3 license is OK, or let us know which you prefer if it's not. (We can keep blueoak in mind for the future)
2) I'll need the domain name(s) and transfer auth code for each we want the Foundation to take over registration for.
3) I think @loziniak has all the sources transferred, so new hosting can be handled after that, and just answering questions we may have in getting things up and running.

Please confirm @loziniak.

Maciej Łoziński
@loziniak
Confirmed. Most important is the license (pt. 1) to allow any modifications. Temporarily it can be hosted by GitHub Pages.
pt. 3 – I have all the sources, also uploaded it to GitHub: https://github.com/redbyexample/red-by-example
Maciej Łoziński
@loziniak
temporary (?) red-by-example home: https://redbyexample.github.io/
Gregg Irwin
@greggirwin
Excellent, thanks. :+1:
VaZub
@vazub
Does anyone have permissions to upload images to rosettacode.org? I've implemented a task for drawing Voronoi diagrams there (https://rosettacode.org/wiki/Voronoi_diagram#Red), but can not upload the output image :(
hiiamboris
@hiiamboris
@vazub
>> random white
== 160.36.66
>> random 500x500
== 151x113
VaZub
@vazub
@hiiamboris updated! thanks)
hiiamboris
@hiiamboris
:+1:
Dorzhi
@tdorzhi
hello
anyone tried to get red + vscode working on NixOS? what I have not working is LSP and compilation
I tried with red 0.6.3 (from nix packages) and red daily build (05-jan-2020) to no avail
hiiamboris
@hiiamboris
Just curious, how do you run nightly builds on NixOS?
Dorzhi
@tdorzhi
downloaded from website
there ain't daily builds in nix packages :(
hiiamboris
@hiiamboris
Hmm. AFAIK NixOS does not allow you to run normal ELF executables without patching/packaging/virtualization. I wonder what's your method.
Dorzhi
@tdorzhi
Oh I understand the question now, and no, nightly build doesn't run, bash says that executable of red not found, although it's right there...
hiiamboris
@hiiamboris
I see. Thanks
Personally I haven't invested enough time into the problem to deal with it. But it got me curious what were the developers of NixOS thinking, making so much trouble out of nowhere ;)
Ask in https://gitter.im/red/red maybe there are some NixOS guys around there.
Dorzhi
@tdorzhi
@hiiamboris thanks, Boris, will do
hiiamboris
@hiiamboris
:+1:
mikeparr
@mikeparr
@greggirwin sorry for delay re RBE site stuff - I'm discussing with Arie now.
Maciej Łoziński
@loziniak
Another RBE news – I've got red-by-example username released, so we can use it for a GitHub organisation.
Maciej Łoziński
@loziniak
Gregg Irwin
@greggirwin
Thanks to both of you!
Dave Andersen
@dander
That's great! So presumably, the red-by-example.org domain could also be used for the GitHub host, correct?
Semseddin Moldibi
@endo64
@dander Yes, it should be.
GiuseppeChillemi
@GiuseppeChillemi

I propose to add an entry the RED/REBOL differences wiki page based on this:
https://gitter.im/red/help?at=5e1b3974dbacf55b3df4d4c4

It should be good as point 4 but I do know the correct terms to write it. I would express such idea:

"In REBOL a function could be passed as value if you precede the argument name with :. In RED this operation passes the unevaluated word. To pass a function as value to another function, precede it with : when calling a function as :print"

Do you think its is generally correct ? If yes, I would modify the wiki and later someone could extend/revise it.

Gregg Irwin
@greggirwin
I think there are notes somewhere that detail lit-word/get-word params, written by @9214 or @hiiamboris perhaps.
GiuseppeChillemi
@GiuseppeChillemi
@greggirwin So it's not a hallucination, I remember these notes to from Vladimir, but I can't find them.
Nenad Rakocevic
@dockimbel
@GiuseppeChillemi As @hiiamboris told you already in red/help, it's a difference between Rebol2 and Rebol3. Red just follows Rebol3 on that. Moreover, this behavior might be changed in the future. Also, please learn to spell "Red" language name properly (it's not "RED").
GiuseppeChillemi
@GiuseppeChillemi
@dockimbel It's a difference it is worth documenting. We could write it could be subject to change. As for RED - > Red, I will try to get the new habit. I am still writing REBOL, old behavior is difficult to change but not impossible.
GiuseppeChillemi
@GiuseppeChillemi
@dockimbel Thanks, we should add a link to the Red/Rebol differences wiki entry or copy the whole text. I will do it after 24h from the current message if no one will reply otherwise.
Nenad Rakocevic
@dockimbel
@greggirwin I leave that matter to you to deal with. :-)
GiuseppeChillemi
@GiuseppeChillemi
Poor Gregg !
hiiamboris
@hiiamboris
Personally I see that Rebol/Red differences page as a sandbox where pioneers can leave a mark and feel happy about it. The point of it in raising community spirit by letting some involvement. In reality there are so many differences between R2 and R3, R3 and Red, R2 and Red, that there will never be a document that covers them all. Why even care what's written on that page? ;)
Gregg Irwin
@greggirwin
It is mainly for Rebolers who may trip over the same common issues.
GiuseppeChillemi
@GiuseppeChillemi
Yes Gregg, I am working on code which runs un both Red and Rebol and having those differences is important.
Nenad Rakocevic
@dockimbel

@hiiamboris

Why even care what's written on that page? ;)

It's part of the red/red repo, so we do care about what's there because ultimately, we are the one responsible for that content (both morally and legally). If the info there is not to be moderated by us, we should just close it and let others mirror it on their own repo, where they can happily fill it with inaccurate or useless info. Another option is to restrict the wiki write access to repo members only.

hiiamboris
@hiiamboris
view [origin 100x50 text red "test"]

I've nothing against symmetry ;) But is this documented anywhere that origin also sets bottom-right padding?
Gregg Irwin
@greggirwin
That should be added to docs, as it is by design. Though origin could do what the name says, and margin could be a new word that provides symmetry.