Re: PicoLisp Wiki: Embed Content?
Hi Alex, thanks! And in case it's a personal private wiki one could even outcomment the new syntax element and eliminate the check for an schrieb am Do., 13. Okt. 2022, 08:24: > Hi Thorsten, > > > I thought about security too. I even would like to have 2 embed options, > > one only for iframes, the other for any html (produced by an external > tool) > > This is indeed a potential security risk. A public Wiki can be edited by > everyone and malicious HTML code might sneak in. > > As discussed yesterday, I commented the change in the release and on the > public > site. It is useful in environments where edit access is controlled, so it > can be > un-commented in such cases. > > Released. > > ☺/ A!ex > > -- > UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe >
Re: PicoLisp Wiki: Embed Content?
Hi Thorsten, > I thought about security too. I even would like to have 2 embed options, > one only for iframes, the other for any html (produced by an external tool) This is indeed a potential security risk. A public Wiki can be edited by everyone and malicious HTML code might sneak in. As discussed yesterday, I commented the change in the release and on the public site. It is useful in environments where edit access is controlled, so it can be un-commented in such cases. Released. ☺/ A!ex -- UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe
Re: PicoLisp Wiki: Embed Content?
Hi Alex, simplification looks good, will test later. I thought about security too. I even would like to have 2 embed options, one only for iframes, the other for any html (produced by an external tool)
Re: PicoLisp Wiki: Embed Content?
Hi Thorsten,
> it's actually extremely easy to embed content in a picolisp wiki file, when
> adding the syntax element from the PS 1 to wiki/lib.l :
> §{ }
> ...
> Would you consider to add something like this in wiki/lib.l ?
Yes, sounds like a good idea :)
> or better a check like this, then if the §{content} does not start with
>
> ("§" # > iframe
> (let Lnk (till "}" T)
> (if (= "(prin Lnk)
>(ht:Prin Lnk) ) ) )
Thanks!!
I simplified this a little to:
("§" # iframe
(let Lnk (till "}" T)
((if (pre? "mailto:picolisp@software-lab.de?subject=Unsubscribe
Re: PicoLisp Wiki: Embed Content?
PS
or better a check like this, then if the §{content} does not start with
:
> Hi Alex,
> it's actually extremely easy to embed content in a picolisp wiki file,
> when adding the syntax element from the PS 1 to wiki/lib.l :
> §{ }
> I added a little check for syntax user cannot insert any kind of code.
>
> With this element its easy to embed youtube videos in wiki pages, they all
> have an embed link (see PS 2)
>
> Would you consider to add something like this in wiki/lib.l ?
> Cheers
> Thorsten
>
>
>
> PS 1
>
>
> 1 file changed, 5 insertions(+), 1 deletion(-)
>
>
> lib.l | 6
>
> +-
>
>
> modified lib.l
>
>
> @@ -54,7 +54,7 @@
>
>
> (recur (Nest)
>
>
> (use C
>
>
> (loop
>
>
>- (ht:Prin (till "^J123456&/!_*+-%~|<@>=\^:$\\#}" T))
>
>
> + (ht:Prin (till "^J123456&/!_*+-%~|<@>=\^:$\\#§}" T))
>
>
> (NIL (setq C (char)))
>
>
> (T (and Nest (= C "}")))
>
>
> (unless (= C "\\")
>
>
> @@ -159,6 +159,10 @@
>
>
> (renderBlock ht:Prin)) )
>
>
> ("\\" (prin "{")) # Escaped brace
>
>
> ("#" (renderBlock prog)) # Comment
>
>
> + ("§" # iframe
>
>
> + (let Lnk (till "}" T)
>
>
> + (when (= " (chop Lnk) " ")
>
> + (prin Lnk) ) )
>
>
> (T (prin C "{")) ) )
>
>
> (T (ht:Prin C)) ) ) ) ) ) ) )
>
>
> PS 2
> https://www.youtube.com/embed/k7CHDscLREk; title="YouTube video player"
> frameborder="0" allow="accelerometer; autoplay; clipboard-write;
> encrypted-media; gyroscope; picture-in-picture" allowfullscreen>
>
>
> Am So., 17. Juli 2022 um 15:46 Uhr schrieb Alexander Burger <
> a...@software-lab.de>:
>
>> Hi Thorsten,
>>
>> > is there a way to embed content in a PicoLisp Wiki file?
>> > ...
>> > But when sharing e.g. a youtube video, there is the "embed" option, that
>> > gives this iframe:
>> > https://www.youtube.com/embed/xEKHU4zCRpY; title="YouTube video player"
>> > ...
>> > I could not figure out how to include this in a page with the PicoLisp
>> Wiki
>> > Syntax - probably it's not possible?
>>
>> I'm afraid so. I think there is no syntax for that in the markup
>> language. Maybe
>> Erik has an idea?
>>
>> ☺/ A!ex
>>
>> --
>> UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe
>>
>
Re: PicoLisp Wiki: Embed Content?
Hi Alex,
it's actually extremely easy to embed content in a picolisp wiki file, when
adding the syntax element from the PS 1 to wiki/lib.l :
§{ }
I added a little check for =\^:$\\#}" T))
+ (ht:Prin (till "^J123456&/!_*+-%~|<@>=\^:$\\#§}" T))
(NIL (setq C (char)))
(T (and Nest (= C "}")))
(unless (= C "\\")
@@ -159,6 +159,10 @@
(renderBlock ht:Prin)) )
("\\" (prin "{")) # Escaped brace
("#" (renderBlock prog)) # Comment
+ ("§" # iframe
+ (let Lnk (till "}" T)
+ (when (= "https://www.youtube.com/embed/k7CHDscLREk; title="YouTube video player"
frameborder="0" allow="accelerometer; autoplay; clipboard-write;
encrypted-media; gyroscope; picture-in-picture" allowfullscreen>
Am So., 17. Juli 2022 um 15:46 Uhr schrieb Alexander Burger <
a...@software-lab.de>:
> Hi Thorsten,
>
> > is there a way to embed content in a PicoLisp Wiki file?
> > ...
> > But when sharing e.g. a youtube video, there is the "embed" option, that
> > gives this iframe:
> > https://www.youtube.com/embed/xEKHU4zCRpY; title="YouTube video player"
> > ...
> > I could not figure out how to include this in a page with the PicoLisp
> Wiki
> > Syntax - probably it's not possible?
>
> I'm afraid so. I think there is no syntax for that in the markup language
Re: PicoLisp Wiki: Embed Content?
Hi Thorsten, > is there a way to embed content in a PicoLisp Wiki file? > ... > But when sharing e.g. a youtube video, there is the "embed" option, that > gives this iframe: > https://www.youtube.com/embed/xEKHU4zCRpY; title="YouTube video player" > ... > I could not figure out how to include this in a page with the PicoLisp Wiki > Syntax - probably it's not possible? I'm afraid so. I think there is no syntax for that in the markup language. Maybe Erik has an idea? ☺/ A!ex -- UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe
PicoLisp Wiki: Embed Content?
Hi List,
is there a way to embed content in a PicoLisp Wiki file?
I can download the video, add it to the page, and then reference it by
name @{}.
But when sharing e.g. a youtube video, there is the "embed" option, that
gives this iframe:
https://www.youtube.com/embed/xEKHU4zCRpY; title="YouTube video player"
frameborder="0" allow="accelerometer; autoplay; clipboard-write;
encrypted-media; gyroscope; picture-in-picture" allowfullscreen>
I could not figure out how to include this in a page with the PicoLisp Wiki
Syntax - probably it's not possible?
Cheers
Thorsten
Re: Wiki Article: Asynchronous Events and Family IPC
By the way, the picolisp twitter account is great !!! :-) JC > On May 8, 2022, at 14:08, Alexander Burger wrote: > > Hi all, > > a new Wiki article about internal background processing, asynchronous events > and > family IPC in PicoLisp: > > https://picolisp.com/wiki/?background > > I think this was not yet documented anywhere. > > ☺/ A!ex > > -- > UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe -- Jean-Christophe Helary @brandelune https://mac4translators.blogspot.com https://sr.ht/~brandelune/omegat-as-a-book/ -- UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe
Wiki Article: Asynchronous Events and Family IPC
Hi all, a new Wiki article about internal background processing, asynchronous events and family IPC in PicoLisp: https://picolisp.com/wiki/?background I think this was not yet documented anywhere. ☺/ A!ex -- UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe
Re: Wiki design update
Hello Erik,
It looks nice now ! Thank you !
JC
> On Feb 10, 2022, at 10:16, Erik Gustafson wrote:
>
> Hi Jean-Christophe,
>
> There must be a lag [...]
>
> The picolisp server caches css files for 24hrs (I think). You may need to
> refresh
> with e.g. ctrl-shift-r
>
> Current (https://picolisp.com/wiki/wiki/wiki.css) is:
> .code {
>color: #333;
>font-weight: bold;
>font-family: 'Courier New', monospace;
>background: #efefef;
>border-radius: 0.15rem;
>border: 1px solid #aaa;
>padding: 0.05rem 0.2rem;
>margin-right: 1px;
>overflow-x: auto;
>font-size: smaller;
> }
>
> pre.code {
>padding: 0.1rem 0.2rem;
>border-radius: 0.25rem;
>background: -webkit-gradient(linear, left top, right bottom,
> from(#efefef), color-stop(90%), to(#dfdfdf));
>background: -o-linear-gradient(top left, #efefef, 90%, #dfdfdf);
>background: linear-gradient(to bottom right, #efefef, 90%, #dfdfdf);
>-webkit-box-shadow: 1px 1px 1px 0px rgba(0,0,0,0.1);
>box-shadow: 1px 1px 1px 0px rgba(0,0,0,0.1);
> }
>
>
> Though looking at the 'help' page again today has me thinking readability
> is best served with something like:
>
> .code {
>color: #222;
>font-weight: bold;
>font-family: 'Courier New', monospace;
>background: #eee;
>border-radius: 0.15rem;
>padding: 0.05rem 0.2rem;
>margin-right: 1px;
>overflow-x: auto;
>font-size: smaller;
> }
>
> pre.code {
>padding: 0.1rem 0.2rem;
>border-radius: 0.25rem;
> }
>
>
> Also known as "what was there before'' :) And then I can always put the
> shine on the homepage with '${...}'.
>
> Thoughts?
--
Jean-Christophe Helary @brandelune
https://mac4translators.blogspot.com
https://sr.ht/~brandelune/omegat-as-a-book/
--
UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe
Re: Wiki design update
Hi Jean-Christophe,
There must be a lag [...]
>
The picolisp server caches css files for 24hrs (I think). You may need to
refresh
with e.g. ctrl-shift-r
Current (https://picolisp.com/wiki/wiki/wiki.css) is:
code {
color: #333;
font-weight: bold;
font-family: 'Courier New', monospace;
background: #efefef;
border-radius: 0.15rem;
border: 1px solid #aaa;
padding: 0.05rem 0.2rem;
margin-right: 1px;
overflow-x: auto;
font-size: smaller;
}
pre.code {
padding: 0.1rem 0.2rem;
border-radius: 0.25rem;
background: -webkit-gradient(linear, left top, right bottom,
from(#efefef), color-stop(90%), to(#dfdfdf));
background: -o-linear-gradient(top left, #efefef, 90%, #dfdfdf);
background: linear-gradient(to bottom right, #efefef, 90%, #dfdfdf);
-webkit-box-shadow: 1px 1px 1px 0px rgba(0,0,0,0.1);
box-shadow: 1px 1px 1px 0px rgba(0,0,0,0.1);
}
Though looking at the 'help' page again today has me thinking readability
is best served with something like:
code {
color: #222;
font-weight: bold;
font-family: 'Courier New', monospace;
background: #eee;
border-radius: 0.15rem;
padding: 0.05rem 0.2rem;
margin-right: 1px;
overflow-x: auto;
font-size: smaller;
}
pre.code {
padding: 0.1rem 0.2rem;
border-radius: 0.25rem;
}
Also known as "what was there before'' :) And then I can always put the
shine on the homepage with '${...}'.
Thoughts?
Re: Wiki design update
> On Feb 9, 2022, at 12:12, Erik Gustafson wrote:
>
> Hi Jean-Christophe,
>
> The setting on line 247 is not inherited by and that
> cramps the code blocks inside the grey background box.
>
> Oops! It seemed to be inherited in firefox for me. Ok, changed :)
Erik,
There must be a lag because I am still seeing this in wiki.css:
(from l.239)
/* code highlighting */
code {
color: #333;
font-weight: bold;
font-family: 'Courier New', monospace;
background: #efefef;
border-radius: 0.3rem;
border: 1px solid #aaa;
padding: 0 0.2rem;
margin-right: 1px;
overflow-x: auto;
font-size: smaller;
}
pre.code {
border-radius: 0.5rem;
padding: unset;
background: -webkit-gradient(linear, left top, right bottom, from(#efefef),
color-stop(90%), to(#dfdfdf));
background: -o-linear-gradient(top left, #efefef, 90%, #dfdfdf);
background: linear-gradient(to bottom right, #efefef, 90%, #dfdfdf);
-webkit-box-shadow: 1px 1px 1px 0px rgba(0,0,0,0.1);
box-shadow: 1px 1px 1px 0px rgba(0,0,0,0.1);
}
Is it what you have ?
Jean-Christophe
--
Jean-Christophe Helary @brandelune
https://mac4translators.blogspot.com
https://sr.ht/~brandelune/omegat-as-a-book/
--
UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe
Re: Wiki design update
Hi Jean-Christophe, The setting on line 247 is not inherited by and that > cramps the code blocks inside the grey background box. > Oops! It seemed to be inherited in firefox for me. Ok, changed :)
Re: Wiki design update
> On Feb 9, 2022, at 10:20, Erik Gustafson wrote: > > Hi Jean-Christophe, > > Good suggestions, that page looked pretty bad. I've uploaded a new css file > with the changes. Erik, Would you mind adding similar padding values to as there are for ? The setting on line 247 is not inherited by and that cramps the code blocks inside the grey background box. Jean-Christophe -- Jean-Christophe Helary @brandelune https://mac4translators.blogspot.com https://sr.ht/~brandelune/omegat-as-a-book/ -- UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe
Re: Wiki design update
Hi Jean-Christophe, Good suggestions, that page looked pretty bad. I've uploaded a new css file with the changes. Thanks, Erik
Re: Wiki design update
Very nice Erik ! Regarding the border-radius for the tag (currently at 0.3/0.5 for the ), I think something a bit less curved would look better at the box angles: https://picolisp.com/wiki/?help Also, adding just a tiny bit of padding would make the code breath a bit. Cheers, Jean-Christophe > On Feb 8, 2022, at 22:47, Erik Gustafson wrote: > > Hi list, > > I thought the wiki could use an update for 2022. Have a look - picolisp.com > > There's a new take on the logo, the login/edit forms are nicer and better > behaved on mobile. And I threw in some CSS gradients to make it look extra > cool > > Feedback welcome! > > -Erik -- Jean-Christophe Helary @brandelune https://mac4translators.blogspot.com https://sr.ht/~brandelune/omegat-as-a-book/ -- UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe
Wiki design update
Hi list, I thought the wiki could use an update for 2022. Have a look - picolisp.com There's a new take on the logo, the login/edit forms are nicer and better behaved on mobile. And I threw in some CSS gradients to make it look extra cool Feedback welcome! -Erik
Re: Internal WIKI Links do not work on WSL2 Debian
Hi Olaf, *"Did you try 127.0.0.1:5000 <http://127.0.0.1:5000/> instead of localhost:5000 ?"* just as a documentation, my experience is that: 1) WSL2 / w3m : all of these work http://localhost:5000 http://127.0.0.1:5000 http://0.0.0.0:5000 2) WIN10 / edge : only this works http://localhost:5000 Cheers Thorsten Am Mi., 19. Jan. 2022 um 14:43 Uhr schrieb O.Hamann : > Hi Thorsten, thanks for your solution! > > Just to be curious: > Did you try 127.0.0.1:5000 instead of localhost:5000 ? > Same pn-replacing effect? > > Regards, Olaf > > > On 19.01.22 00:20, Thorsten Jolitz wrote: > > Hi List, > > today I figured out what seems to be the problem here: > > Somehow the URLs are built with the computername instead of the port: > > http://0.0.0.0:asuspn/?home > > > > Replacing asuspn with 5000 all of these work, even from (say) Edge in > > Win10, when pil wiki server was started on WSL2: > > > > http://localhost:5000/?home > > http://localhost:5000/?help > > http://localhost:5000/?*Menu=+0&*Tab=+1&*ID=&*ID=$login > > > > with the last one, I can actually login, get a session id, and can > > navigate in the wiki and in my account. > > Strange, the port looks ok in the server call, and on Archlinux the URLs > > are ok too, but on WSL2 the servername instead of port is used to build > > the URL. > > > > $ pil wiki/main.l -main -go + > > (server (or (format (sys "PORT")) *WikiPort) "!wiki") > > ! *WikiPort > > -> 5000 > > > > Cheers > > Thorsten > > > > PS > > I start the wiki the normal way > > $ pil wiki/main.l -main -go + > > *Socket > > 1877 = 40895 20654634285828729~ > > : *Socket > > -> NIL > > : 1877 * 2022-01-19 00:00:37 admin > > 1883 = 57451 41629218673747370~ > > : > > > > > > > > Am Di., 28. Dez. 2021 um 23:42 Uhr schrieb Thorsten Jolitz > > mailto:tjol...@gmail.com>>: > > > > Hi Alex, > > yes, *ID is NIL when I debug it (see PS1). > > I'm not sure how to debug (app), but all global vars except *PID > > seem to be NIL ... > > > > I think it's a WSL2 localhost problem, not a bug in PicoLisp. > > Not too long ago I tried accessing the pil wiki server running on > > WSL2 from the Win10 Browser (say Edge), and that did not work at all > > Now it seems they have fixed that ,what is very nice, but still not > > the same like pure Linux apparently. > > > > Checking localhost everything seems normal (see PS 2) , but e.g this > > article describes a lot of problems: > > Fixing WSL2 localhost access issue - abdus.dev > > <https://abdus.dev/posts/fixing-wsl2-localhost-access-issue/> > > > > Cheers > > Thorsten > > > > PS 1 > > $ pil wiki/main.l -main -go + > > (and (== 'login *ID) (app)) > > ! *ID > > -> NIL > > ! (setq *ID 123456789) # naive try > > -> 123456789 > > > > # naiv try did not work > > Can't load -2.html?*Menu=+0&*Tab=+1&*ID=+123456789&*ID=$login > > > > PS 2 > > $ ping -a localhost > > PING localhost (127.0.0.1) 56(84) bytes of data. > > > > # type c (peek current url) in W3M : wiki start page > > http://localhost:8080/ > > > > # $ sudo cat /etc/hosts > > 127.0.0.1 localhost > > 127.0.1.1 xyz.localdomain xyz > > > > Am Di., 28. Dez 2021 um 20:44 Uhr schrieb Alexander Burger > > mailto:a...@software-lab.de>>: > > > > Hi Thorsten, Olaf, > > > > > it's a session problem. > > > Port 8080 does not help, but I cross checked on Archlinux, > > when I first > > > click on the Login link, a session prefix is added to the > > internal links, > > > and after login, that session prefix is everywhere in the html > > source. > > > But on WSL2 that does not work somehow > > > > This is indeed strange. This logic should not depend on the > system. > > > > I think the session is started after clicking on "Log in" in > > > >(dm (html> . +Doc) () > > (and (== 'login *ID) (app)) > > > > So somehow this check fails? The *ID value is passed on the URL, > > perhaps it is > > destroyed somehow? The browser? > > > > ☺/ A!ex > > > > -- > > UNSUBSCRIBE: mailto:picolisp@software-lab.de > > <mailto:picolisp@software-lab.de>?subject=Unsubscribe > > > > -- > UNSUBSCRIBE: mailto:picolisp@software-lab.de?subjectUnsubscribe >
Re: Internal WIKI Links do not work on WSL2 Debian
Hi Alex,
yes, $NAME was the computername ("asuspn"), and by setting name to
$ echo $NAME
5000
everything works, I even get the wiki page with CSS then like in the real
wiki.
So, problem identified and solved, thanks!
Cheers
Thorsten
Am Mi., 19. Jan. 2022 um 17:56 Uhr schrieb Alexander Burger <
a...@software-lab.de>:
> Hi Thorsten,
>
> > I looks actually as designed:
> > in function baseHRef in http.l is this line
> >
> > (or Port (if *SesId *Port *Port1))
> >
> > and *Port1 is the Computername.
>
> Correct, though not the Computername.
>
> IFF the PicoLisp server is started behind a httqGate, the "port" is the
> application name. For example, on picolisp.com, the httpGate config file
> has a
> line
>
>wiki 5000 app /home/app log/wiki pil21/pil wiki/main.l @lib/app.l -main
> patch.l -go -wait +
>
> so that httpGate translates "wiki" in requests to 5000.
>
> The question is how this happens in your setup:
>
> *Port1 is assigned in the 'server' function from the "NAME" environment
> variable. So I suspect $NAME is set in your env to the machine's name, and
> not
> overridden by httpGate. That would explain it!
>
> You could unset NAME in your shell before starting PicoLisp, or (even
> better)
> use httpGate.
>
> ☺/ A!ex
>
> --
> UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe
>
Re: Internal WIKI Links do not work on WSL2 Debian
Hi Thorsten, > I looks actually as designed: > in function baseHRef in http.l is this line > > (or Port (if *SesId *Port *Port1)) > > and *Port1 is the Computername. Correct, though not the Computername. IFF the PicoLisp server is started behind a httqGate, the "port" is the application name. For example, on picolisp.com, the httpGate config file has a line wiki 5000 app /home/app log/wiki pil21/pil wiki/main.l @lib/app.l -main patch.l -go -wait + so that httpGate translates "wiki" in requests to 5000. The question is how this happens in your setup: *Port1 is assigned in the 'server' function from the "NAME" environment variable. So I suspect $NAME is set in your env to the machine's name, and not overridden by httpGate. That would explain it! You could unset NAME in your shell before starting PicoLisp, or (even better) use httpGate. ☺/ A!ex -- UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe
Re: Internal WIKI Links do not work on WSL2 Debian
Hi Alex, Hi Olaf, I would not say I found a "solution", just trying to figure out the cause. I looks actually as designed: in function baseHRef in http.l is this line (or Port (if *SesId *Port *Port1)) and *Port1 is the Computername. So apparently the landing page is build with these URLs with name instead of port, and only once a session id is acquired, a numeric port is used. These links are dead on the landing page, but when I enter the URLs in the browser, they work, e.g. http://localhost:5000/?help. Once I enter this in the browser: http://localhost:5000/?*Menu=+0&*Tab=+1&*ID=&*ID=$login , and login, all the links work again on the page, since a *'SesId exists and they are build with the port number (e.g. http://localhost:49651/62212780669042004~?Help) I wonder how these links http://localhost:asuspn/?help <http://localhost:5000/?help> http://localhost:asuspn/?h <http://localhost:5000/?help>ome are supposed to work before a session id is acquired, but somehow they do work on normal Linux. Since (session P H) is called with the Port P (5000), why not use it for URL construction (instead of *Port1)? Cheers Thorsten PS (out 2 (prinl *Pid " = " *Port " " *SesId)) 1549 = 49651 62212780669042004~ (or "Port" (if *SesId *Port *Port1)) (or "Port" (if *SesId *Port *Port1)) (or "Port" (if *SesId *Port *Port1)) (or "Port" (if *SesId *Port *Port1)) (or *SesId (bye)) : 1549 * 2022-01-19 17:07:16 admin Am Mi., 19. Jan. 2022 um 14:43 Uhr schrieb O.Hamann : > Hi Thorsten, thanks for your solution! > > Just to be curious: > Did you try 127.0.0.1:5000 instead of localhost:5000 ? > Same pn-replacing effect? > > Regards, Olaf > > > On 19.01.22 00:20, Thorsten Jolitz wrote: > > Hi List, > > today I figured out what seems to be the problem here: > > Somehow the URLs are built with the computername instead of the port: > > http://0.0.0.0:asuspn/?home > > > > Replacing asuspn with 5000 all of these work, even from (say) Edge in > > Win10, when pil wiki server was started on WSL2: > > > > http://localhost:5000/?home > > http://localhost:5000/?help > > http://localhost:5000/?*Menu=+0&*Tab=+1&*ID=&*ID=$login > > > > with the last one, I can actually login, get a session id, and can > > navigate in the wiki and in my account. > > Strange, the port looks ok in the server call, and on Archlinux the URLs > > are ok too, but on WSL2 the servername instead of port is used to build > > the URL. > > > > $ pil wiki/main.l -main -go + > > (server (or (format (sys "PORT")) *WikiPort) "!wiki") > > ! *WikiPort > > -> 5000 > > > > Cheers > > Thorsten > > > > PS > > I start the wiki the normal way > > $ pil wiki/main.l -main -go + > > *Socket > > 1877 = 40895 20654634285828729~ > > : *Socket > > -> NIL > > : 1877 * 2022-01-19 00:00:37 admin > > 1883 = 57451 41629218673747370~ > > : > > > > > > > > Am Di., 28. Dez. 2021 um 23:42 Uhr schrieb Thorsten Jolitz > > mailto:tjol...@gmail.com>>: > > > > Hi Alex, > > yes, *ID is NIL when I debug it (see PS1). > > I'm not sure how to debug (app), but all global vars except *PID > > seem to be NIL ... > > > > I think it's a WSL2 localhost problem, not a bug in PicoLisp. > > Not too long ago I tried accessing the pil wiki server running on > > WSL2 from the Win10 Browser (say Edge), and that did not work at all > > Now it seems they have fixed that ,what is very nice, but still not > > the same like pure Linux apparently. > > > > Checking localhost everything seems normal (see PS 2) , but e.g this > > article describes a lot of problems: > > Fixing WSL2 localhost access issue - abdus.dev > > <https://abdus.dev/posts/fixing-wsl2-localhost-access-issue/> > > > > Cheers > > Thorsten > > > > PS 1 > > $ pil wiki/main.l -main -go + > > (and (== 'login *ID) (app)) > > ! *ID > > -> NIL > > ! (setq *ID 123456789) # naive try > > -> 123456789 > > > > # naiv try did not work > > Can't load -2.html?*Menu=+0&*Tab=+1&*ID=+123456789&*ID=$login > > > > PS 2 > > $ ping -a localhost > > PING localhost (127.0.0.1) 56(84) bytes of data. > > > > # type c (peek current url) in W3M : wiki start page > > http://localhost:8080/ > > > > # $ sudo cat /etc/hosts > > 127.0.0.1 localhost > > 1
Re: Internal WIKI Links do not work on WSL2 Debian
Hi Thorsten, thanks for your solution! Just to be curious: Did you try 127.0.0.1:5000 instead of localhost:5000 ? Same pn-replacing effect? Regards, Olaf On 19.01.22 00:20, Thorsten Jolitz wrote: > Hi List, > today I figured out what seems to be the problem here: > Somehow the URLs are built with the computername instead of the port: > http://0.0.0.0:asuspn/?home > > Replacing asuspn with 5000 all of these work, even from (say) Edge in > Win10, when pil wiki server was started on WSL2: > > http://localhost:5000/?home > http://localhost:5000/?help > http://localhost:5000/?*Menu=+0&*Tab=+1&*ID=&*ID=$login > > with the last one, I can actually login, get a session id, and can > navigate in the wiki and in my account. > Strange, the port looks ok in the server call, and on Archlinux the URLs > are ok too, but on WSL2 the servername instead of port is used to build > the URL. > > $ pil wiki/main.l -main -go + > (server (or (format (sys "PORT")) *WikiPort) "!wiki") > ! *WikiPort > -> 5000 > > Cheers > Thorsten > > PS > I start the wiki the normal way > $ pil wiki/main.l -main -go + > *Socket > 1877 = 40895 20654634285828729~ > : *Socket > -> NIL > : 1877 * 2022-01-19 00:00:37 admin > 1883 = 57451 41629218673747370~ > : > > > > Am Di., 28. Dez. 2021 um 23:42 Uhr schrieb Thorsten Jolitz > mailto:tjol...@gmail.com>>: > > Hi Alex, > yes, *ID is NIL when I debug it (see PS1). > I'm not sure how to debug (app), but all global vars except *PID > seem to be NIL ... > > I think it's a WSL2 localhost problem, not a bug in PicoLisp. > Not too long ago I tried accessing the pil wiki server running on > WSL2 from the Win10 Browser (say Edge), and that did not work at all > Now it seems they have fixed that ,what is very nice, but still not > the same like pure Linux apparently. > > Checking localhost everything seems normal (see PS 2) , but e.g this > article describes a lot of problems: > Fixing WSL2 localhost access issue - abdus.dev > <https://abdus.dev/posts/fixing-wsl2-localhost-access-issue/> > > Cheers > Thorsten > > PS 1 > $ pil wiki/main.l -main -go + > (and (== 'login *ID) (app)) > ! *ID > -> NIL > ! (setq *ID 123456789) # naive try > -> 123456789 > > # naiv try did not work > Can't load -2.html?*Menu=+0&*Tab=+1&*ID=+123456789&*ID=$login > > PS 2 > $ ping -a localhost > PING localhost (127.0.0.1) 56(84) bytes of data. > > # type c (peek current url) in W3M : wiki start page > http://localhost:8080/ > > # $ sudo cat /etc/hosts > 127.0.0.1 localhost > 127.0.1.1 xyz.localdomain xyz > > Am Di., 28. Dez 2021 um 20:44 Uhr schrieb Alexander Burger > mailto:a...@software-lab.de>>: > > Hi Thorsten, Olaf, > > > it's a session problem. > > Port 8080 does not help, but I cross checked on Archlinux, > when I first > > click on the Login link, a session prefix is added to the > internal links, > > and after login, that session prefix is everywhere in the html > source. > > But on WSL2 that does not work somehow > > This is indeed strange. This logic should not depend on the system. > > I think the session is started after clicking on "Log in" in > > (dm (html> . +Doc) () > (and (== 'login *ID) (app)) > > So somehow this check fails? The *ID value is passed on the URL, > perhaps it is > destroyed somehow? The browser? > > ☺/ A!ex > > -- > UNSUBSCRIBE: mailto:picolisp@software-lab.de > <mailto:picolisp@software-lab.de>?subject=Unsubscribe > -- UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe
Re: Internal WIKI Links do not work on WSL2 Debian
Hi Thorsten, > today I figured out what seems to be the problem here: > Somehow the URLs are built with the computername instead of the port: > http://0.0.0.0:asuspn/?home > > Replacing asuspn with 5000 all of these work, even from (say) Edge in > Win10, when pil wiki server was started on WSL2: This is really strange. Who is building this URL? Is it the PicoLisp server when packing " ! *WikiPort > -> 5000 > > Cheers > Thorsten > > PS > I start the wiki the normal way > $ pil wiki/main.l -main -go + > *Socket > 1877 = 40895 20654634285828729~ > : *Socket > -> NIL > : 1877 * 2022-01-19 00:00:37 admin > 1883 = 57451 41629218673747370~ ☺/ A!ex -- UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe
Re: Internal WIKI Links do not work on WSL2 Debian
Hi List, today I figured out what seems to be the problem here: Somehow the URLs are built with the computername instead of the port: http://0.0.0.0:asuspn/?home Replacing asuspn with 5000 all of these work, even from (say) Edge in Win10, when pil wiki server was started on WSL2: http://localhost:5000/?home http://localhost:5000/?help http://localhost:5000/?*Menu=+0&*Tab=+1&*ID=&*ID=$login with the last one, I can actually login, get a session id, and can navigate in the wiki and in my account. Strange, the port looks ok in the server call, and on Archlinux the URLs are ok too, but on WSL2 the servername instead of port is used to build the URL. $ pil wiki/main.l -main -go + (server (or (format (sys "PORT")) *WikiPort) "!wiki") ! *WikiPort -> 5000 Cheers Thorsten PS I start the wiki the normal way $ pil wiki/main.l -main -go + *Socket 1877 = 40895 20654634285828729~ : *Socket -> NIL : 1877 * 2022-01-19 00:00:37 admin 1883 = 57451 41629218673747370~ : Am Di., 28. Dez. 2021 um 23:42 Uhr schrieb Thorsten Jolitz < tjol...@gmail.com>: > Hi Alex, > yes, *ID is NIL when I debug it (see PS1). > I'm not sure how to debug (app), but all global vars except *PID seem to > be NIL ... > > I think it's a WSL2 localhost problem, not a bug in PicoLisp. > Not too long ago I tried accessing the pil wiki server running on WSL2 > from the Win10 Browser (say Edge), and that did not work at all. > Now it seems they have fixed that ,what is very nice, but still not the > same like pure Linux apparently. > > Checking localhost everything seems normal (see PS 2) , but e.g this > article describes a lot of problems: > Fixing WSL2 localhost access issue - abdus.dev > <https://abdus.dev/posts/fixing-wsl2-localhost-access-issue/> > > Cheers > Thorsten > > PS 1 > $ pil wiki/main.l -main -go + > (and (== 'login *ID) (app)) > ! *ID > -> NIL > ! (setq *ID 123456789) # naive try > -> 123456789 > > # naiv try did not work > Can't load -2.html?*Menu=+0&*Tab=+1&*ID=+123456789&*ID=$login > > PS 2 > $ ping -a localhost > PING localhost (127.0.0.1) 56(84) bytes of data. > > # type c (peek current url) in W3M : wiki start page > http://localhost:8080/ > > # $ sudo cat /etc/hosts > 127.0.0.1 localhost > 127.0.1.1 xyz.localdomain xyz > > Am Di., 28. Dez. 2021 um 20:44 Uhr schrieb Alexander Burger < > a...@software-lab.de>: > >> Hi Thorsten, Olaf, >> >> > it's a session problem. >> > Port 8080 does not help, but I cross checked on Archlinux, when I first >> > click on the Login link, a session prefix is added to the internal >> links, >> > and after login, that session prefix is everywhere in the html source. >> > But on WSL2 that does not work somehow >> >> This is indeed strange. This logic should not depend on the system. >> >> I think the session is started after clicking on "Log in" in >> >>(dm (html> . +Doc) () >> (and (== 'login *ID) (app)) >> >> So somehow this check fails? The *ID value is passed on the URL, perhaps >> it is >> destroyed somehow? The browser? >> >> ☺/ A!ex >> >> -- >> UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe >> >
Re: Internal WIKI Links do not work on WSL2 Debian
Hi Alex, yes, *ID is NIL when I debug it (see PS1). I'm not sure how to debug (app), but all global vars except *PID seem to be NIL ... I think it's a WSL2 localhost problem, not a bug in PicoLisp. Not too long ago I tried accessing the pil wiki server running on WSL2 from the Win10 Browser (say Edge), and that did not work at all. Now it seems they have fixed that ,what is very nice, but still not the same like pure Linux apparently. Checking localhost everything seems normal (see PS 2) , but e.g this article describes a lot of problems: Fixing WSL2 localhost access issue - abdus.dev <https://abdus.dev/posts/fixing-wsl2-localhost-access-issue/> Cheers Thorsten PS 1 $ pil wiki/main.l -main -go + (and (== 'login *ID) (app)) ! *ID -> NIL ! (setq *ID 123456789) # naive try -> 123456789 # naiv try did not work Can't load -2.html?*Menu=+0&*Tab=+1&*ID=+123456789&*ID=$login PS 2 $ ping -a localhost PING localhost (127.0.0.1) 56(84) bytes of data. # type c (peek current url) in W3M : wiki start page http://localhost:8080/ # $ sudo cat /etc/hosts 127.0.0.1 localhost 127.0.1.1 xyz.localdomain xyz Am Di., 28. Dez. 2021 um 20:44 Uhr schrieb Alexander Burger < a...@software-lab.de>: > Hi Thorsten, Olaf, > > > it's a session problem. > > Port 8080 does not help, but I cross checked on Archlinux, when I first > > click on the Login link, a session prefix is added to the internal links, > > and after login, that session prefix is everywhere in the html source. > > But on WSL2 that does not work somehow > > This is indeed strange. This logic should not depend on the system. > > I think the session is started after clicking on "Log in" in > >(dm (html> . +Doc) () > (and (== 'login *ID) (app)) > > So somehow this check fails? The *ID value is passed on the URL, perhaps > it is > destroyed somehow? The browser? > > ☺/ A!ex > > -- > UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe >
Re: Internal WIKI Links do not work on WSL2 Debian
Hi Thorsten, Olaf, > it's a session problem. > Port 8080 does not help, but I cross checked on Archlinux, when I first > click on the Login link, a session prefix is added to the internal links, > and after login, that session prefix is everywhere in the html source. > But on WSL2 that does not work somehow This is indeed strange. This logic should not depend on the system. I think the session is started after clicking on "Log in" in (dm (html> . +Doc) () (and (== 'login *ID) (app)) So somehow this check fails? The *ID value is passed on the URL, perhaps it is destroyed somehow? The browser? ☺/ A!ex -- UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe
Re: Internal WIKI Links do not work on WSL2 Debian
Hallo Olaf, it's a session problem. Port 8080 does not help, but I cross checked on Archlinux, when I first click on the Login link, a session prefix is added to the internal links, and after login, that session prefix is everywhere in the html source. But on WSL2 that does not work somehow, I cleaned up the Wiki DB and started again, but same problem Regards, Thorsten PS Before that, the links look the same: WSL2/Debian Log in Archlinux: Log in => click on login Log in Am Di., 28. Dez. 2021 um 16:27 Uhr schrieb O.Hamann : > And another idea: > > Did you try other more common ports, sth. like 8080 or so? > (in case there is some firewall mechanism blocking, or so?) > > Regards, Olaf > > > On 24.12.21 14:06, Thorsten Jolitz wrote: > > Hi List, > > I have the newest pil21 and the current picolisp wiki running on > > - Win10 / WSL2 (Debian unstable) > > - Archlinux > > and while in both cases I do see the start page of the wiki on > > http://localhost:5000, only the external Menu links work on WSL2, not > > the wiki internal links (nor the login). > > > > What is quite nice now, on Win10 I can access the running wiki server on > > localhost from WSL2/Debian (via W3M) and from the Windows browser > > (chrome or edge), I think that didn't work before. > > > > But these kind of links do not work in either case, > > > href="-2.html?*Menu=+0&*Tab=+1&*ID=&*ID=$login">Log in > > > > W3M says: "Can't load -2.html?*Menu=+0&*Tab=+1&*ID=&*ID=$login", while > > Edge shows "about:blank#blocked". I started the server in debug mode > > (pil wiki/main.l -main -go +), but no messages show up in the server > > window. > > > > Did anyone experience the same issue? > > Cheers > > Thorsten > > -- > UNSUBSCRIBE: mailto:picolisp@software-lab.de?subjectUnsubscribe >
Re: Internal WIKI Links do not work on WSL2 Debian
And another idea: Did you try other more common ports, sth. like 8080 or so? (in case there is some firewall mechanism blocking, or so?) Regards, Olaf On 24.12.21 14:06, Thorsten Jolitz wrote: > Hi List, > I have the newest pil21 and the current picolisp wiki running on > - Win10 / WSL2 (Debian unstable) > - Archlinux > and while in both cases I do see the start page of the wiki on > http://localhost:5000, only the external Menu links work on WSL2, not > the wiki internal links (nor the login). > > What is quite nice now, on Win10 I can access the running wiki server on > localhost from WSL2/Debian (via W3M) and from the Windows browser > (chrome or edge), I think that didn't work before. > > But these kind of links do not work in either case, > href="-2.html?*Menu=+0&*Tab=+1&*ID=&*ID=$login">Log in > > W3M says: "Can't load -2.html?*Menu=+0&*Tab=+1&*ID=&*ID=$login", while > Edge shows "about:blank#blocked". I started the server in debug mode > (pil wiki/main.l -main -go +), but no messages show up in the server > window. > > Did anyone experience the same issue? > Cheers > Thorsten -- UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe
Re: Internal WIKI Links do not work on WSL2 Debian
Hi Thorsten, could it be, that the URL in href="-2.html" is missing a prefix, which would be provided by a pil21 global var or function but in your case is or returns NIL ? when I'm looking on picolisp.com the Login Link URL looks like this: https://picolisp.com/36959/20150297173518751~-A4.html?*Menu.. so perhaps in your case the session url handling is missing? Did you already solve this issue or is it still worthy to look into it? I think, I had a somehow comparable issue some time ago. Greetings, Olaf On 24.12.21 14:06, Thorsten Jolitz wrote: > Hi List, > I have the newest pil21 and the current picolisp wiki running on > - Win10 / WSL2 (Debian unstable) > - Archlinux > and while in both cases I do see the start page of the wiki on > http://localhost:5000, only the external Menu links work on WSL2, not > the wiki internal links (nor the login). > > What is quite nice now, on Win10 I can access the running wiki server on > localhost from WSL2/Debian (via W3M) and from the Windows browser > (chrome or edge), I think that didn't work before. > > But these kind of links do not work in either case, > href="-2.html?*Menu=+0&*Tab=+1&*ID=&*ID=$login">Log in > > W3M says: "Can't load -2.html?*Menu=+0&*Tab=+1&*ID=&*ID=$login", while > Edge shows "about:blank#blocked". I started the server in debug mode > (pil wiki/main.l -main -go +), but no messages show up in the server > window. > > Did anyone experience the same issue? > Cheers > Thorsten -- UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe
Internal WIKI Links do not work on WSL2 Debian
Hi List, I have the newest pil21 and the current picolisp wiki running on - Win10 / WSL2 (Debian unstable) - Archlinux and while in both cases I do see the start page of the wiki on http://localhost:5000, only the external Menu links work on WSL2, not the wiki internal links (nor the login). What is quite nice now, on Win10 I can access the running wiki server on localhost from WSL2/Debian (via W3M) and from the Windows browser (chrome or edge), I think that didn't work before. But these kind of links do not work in either case, Log in W3M says: "Can't load -2.html?*Menu=+0&*Tab=+1&*ID=&*ID=$login", while Edge shows "about:blank#blocked". I started the server in debug mode (pil wiki/main.l -main -go +), but no messages show up in the server window. Did anyone experience the same issue? Cheers Thorsten
Re: wiki function: _render
On Wed, Sep 15, 2021 at 10:49:00PM +0900, Jean-Christophe Helary wrote:
> > What if the value of E is something like
> >
> >">alert('xss');
>
> You mean n{alert('xss');}?
>
> I don't understand Alex’ answer:
> > In final code this would be written as (ht:Prin E)
>
> but I guess he is right :)
I hope so.
(ht:Prin ">alert('xss');")
scriptalert('xss');/script
☺/ A!ex
--
UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe
Re: wiki function: _render
On Sat, Sep 11, 2021 at 07:28:43PM +0200, Tomas Hlavaty wrote:
> On Sat 11 Sep 2021 at 18:11, Jean-Christophe Helary
> wrote:
> >(prin "<" C D " id=\"h" D "-" E "\">")
> > which would give us:
> > My heading
>
> What if the value of E is something like
>
>">alert('xss');
In final code this would be written as (ht:Prin E)
☺/ A!ex
--
UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe
Re: wiki function: _render
On Sat 11 Sep 2021 at 18:11, Jean-Christophe Helary
wrote:
>(prin "<" C D " id=\"h" D "-" E "\">")
> which would give us:
> My heading
What if the value of E is something like
">alert('xss');
--
UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe
Re: wiki function: _render
For one thing, I don’t think NAME is defined on H1-H6 like it is for INPUT
or A.
John
On Sat, Sep 11, 2021 at 05:47 Alexander Burger wrote:
> Hi Jean-Christophe,
>
> > I'm just exploring my very first lines of picolisp code, and it is going
> to
> > take some time to get something done... :)
>
> Very good! :)
>
>
> > The wiki html seems to be generated by _render, which is defined this
> way:
> >
> > (de _render (C D)
> > ...
> > for the code for html headers is:
> >
> > (case C
> > (("1" "2" "3" "4" "5" "6") # Heading
> > (_render "h" C)
> > ...
> > with C being equal to the number that was used to define the header
> (wiki syntax: n{Heading}).
>
> Correct.
>
>
> > So, my first idea would be, instead of adding complexity to the wiki
> syntax to specify ID values, to use the value of the heading as the value
> of the ID and output this:
> >
> > My heading
> >
> > That does not guarantee that we have unique ID values, which is a
> requirement
> > in HTML,
>
> Is there a reason not to use instead?
>
> ☺/ A!ex
>
> --
> UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe
>
--
John Duncan
Re: wiki function: _render
Hi Jean-Christophe,
> I'm just exploring my very first lines of picolisp code, and it is going to
> take some time to get something done... :)
Very good! :)
> The wiki html seems to be generated by _render, which is defined this way:
>
> (de _render (C D)
> ...
> for the code for html headers is:
>
> (case C
> (("1" "2" "3" "4" "5" "6") # Heading
> (_render "h" C)
> ...
> with C being equal to the number that was used to define the header (wiki
> syntax: n{Heading}).
Correct.
> So, my first idea would be, instead of adding complexity to the wiki syntax
> to specify ID values, to use the value of the heading as the value of the ID
> and output this:
>
> My heading
>
> That does not guarantee that we have unique ID values, which is a requirement
> in HTML,
Is there a reason not to use instead?
☺/ A!ex
--
UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe
wiki function: _render
I'm just exploring my very first lines of picolisp code, and it is going to
take some time to get something done... :)
I was mentioning a few days ago that the wiki would benefit from having links
to internal IDs, so as to create a formal table of contents, or just as a way
to link to (relatively) arbitrary places in other pages.
The wiki html seems to be generated by _render, which is defined this way:
(de _render (C D)
(prin "<" C D ">")
(recurse T)
(prin "") )
for the code for html headers is:
(case C
(("1" "2" "3" "4" "5" "6") # Heading
(_render "h" C)
(prinl)
(skip) )
with C being equal to the number that was used to define the header (wiki
syntax: n{Heading}).
The only case where _render uses 2 arguments is for headers.
So, my first idea would be, instead of adding complexity to the wiki syntax to
specify ID values, to use the value of the heading as the value of the ID and
output this:
My heading
That does not guarantee that we have unique ID values, which is a requirement
in HTML, in case the author has the idea/requirement to actually create headers
with the same content... But we can reasonably expect that the author won't
create headers with the same tag value and the same contents unless by mistake.
So maybe adding the header tag to the ID could reduce chances to have
non-unique IDs...
So basically, what we'd need is:
# I'm not clear why the internal variables are labeled C and D, so maybe I'm
missing something here, that may not be arbitrary, but I can't tell...
(de _render (C D E)
(prin "<" C D " id=\"h" D "-" E "\">")
(recurse T)
(prin "") )
which would give us:
My heading
and then, the only thing I need to do (hehehe) is to actually make sure that E
actually gets the value of the heading.
Am I heading (no pun intended) in the right direction ?
--
Jean-Christophe Helary @brandelune
https://mac4translators.blogspot.com
https://sr.ht/~brandelune/omegat-as-a-book/
--
UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe
Re: Wiki modifications
On Thu, Sep 09, 2021 at 12:04:37AM +0900, Jean-Christophe Helary wrote: > > Did you try to upload with the second button? > > > > "Upload CSS File (wiki.css)" > > Ok, let me describe what I did: > > • → https://picolisp.com/wiki/?home > • login > • → my account > • → Documents > • [New] → click > • [Choose file] > • (select wiki.css) > • Specify a name → wiki.css > • [Upload directly] → click > > And nothing visible happens... Ah, sorry! After "my account" not Documents but the "Upload" menu item (between User Administration and Helz). There you are two file choosers. The second one is "Upload CSS File (wiki.css)". ☺/ A!ex -- UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe
Re: Wiki modifications
> On Sep 8, 2021, at 22:19, Alexander Burger wrote: > > Hi Jean-Christophe, > >> I think the file is uploaded now. > > Hmm, are you sure? On the server I still have the old version > from 2020-12-13 12:22:26 > > Did you try to upload with the second button? > > "Upload CSS File (wiki.css)" Ok, let me describe what I did: • → https://picolisp.com/wiki/?home • login • → my account • → Documents • [New] → click • [Choose file] • (select wiki.css) • Specify a name → wiki.css • [Upload directly] → click And nothing visible happens... -- Jean-Christophe Helary @brandelune https://mac4translators.blogspot.com https://sr.ht/~brandelune/omegat-as-a-book/ -- UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe
Re: Wiki modifications
Hi Jean-Christophe, > I think the file is uploaded now. Hmm, are you sure? On the server I still have the old version from 2020-12-13 12:22:26 Did you try to upload with the second button? "Upload CSS File (wiki.css)" If so, it directly copies the uploaded file to wiki/wiki.css Please try again, I'm looking forward to your improvements :) (for the records: The current version is https://software-lab.de/wiki.tgz) ☺/ A!ex -- UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe
Re: Wiki modifications
On 06.09.21 14:01, Jean-Christophe Helary wrote: > 4) I added an "Alternative repository install for macOS" page > https://picolisp.com/wiki/?alternativeMacOSRepository Thank you very much for providing und publishing this! I was able to install a pil21 version on macOS 11.5.2 following the steps of your Howto. There was one message because of not finding pkg-config, but that seems to be acceptable, as /pil @lib/tests.l + finishes with: OK and it was possible to start the documentation index on localhost:8080 cd pil21/doc ./pil @lib/http.l @lib/xhtml.l @lib/form.l --server 8080 index.html -wait (-wait on same line after index.html) So thank you very much for providing and publishing this clear step-by-step instructions! -- UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe
Re: Wiki modifications
Alex, I think the file is uploaded now. I don't want to fiddle too much with the Hn sizes, so what I did is comment out the size parts so that the sizes are taken from the default HTML css with sets them in em, and not in px. That way, there is no real need to use a @media directive for bigger screen sizes. I've checked the wiki with the HTML defaults and there is a good separation between the sizes and the wiki blue color still clearly identifies the parts as headers. As far as I can tell, the site looks more structured this way. But I don't want to force my opinion on others, so feel free to revert, or make further changes. I like css a lot. I've created a personal css for the gnu emacs manuals that uses all the default "hooks" found in the texi conversion. It's not much (and it's not possible to have elisp syntax coloring) but I think it looks way better than the original: https://www.gnu.org/software/emacs/manual/html_node/elisp/Predicates-for-Strings.html https://doublet.jp/gnu%20html/elisp/Predicates-for-Strings.html JC > On Sep 7, 2021, at 0:28, Alexander Burger wrote: > > On Tue, Sep 07, 2021 at 12:08:57AM +0900, Jean-Christophe Helary wrote: >> I've logged in to the Wiki interface but I'm not sure where I'd upload the >> modified file. > > There is an "Upload" menu item in the GUI. There the Logo and wiki.css files > can > be uploaded :) > > ☺/ A!ex > > > -- > UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe -- Jean-Christophe Helary @brandelune https://mac4translators.blogspot.com https://sr.ht/~brandelune/omegat-as-a-book/ -- UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe
Re: Wiki modifications
> On Sep 7, 2021, at 0:28, Alexander Burger wrote: > > On Tue, Sep 07, 2021 at 12:08:57AM +0900, Jean-Christophe Helary wrote: >> I've logged in to the Wiki interface but I'm not sure where I'd upload the >> modified file. > > There is an "Upload" menu item in the GUI. There the Logo and wiki.css files > can > be uploaded :) OK ! I'll do that later this week :-) -- Jean-Christophe Helary @brandelune https://mac4translators.blogspot.com https://sr.ht/~brandelune/omegat-as-a-book/ -- UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe
Re: Wiki modifications
On Tue, Sep 07, 2021 at 12:08:57AM +0900, Jean-Christophe Helary wrote: > I've logged in to the Wiki interface but I'm not sure where I'd upload the > modified file. There is an "Upload" menu item in the GUI. There the Logo and wiki.css files can be uploaded :) ☺/ A!ex -- UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe
Re: Wiki modifications
> On Sep 6, 2021, at 23:29, Alexander Burger wrote: > >> I think I had that in mind when I made my first modifications to the wiki >> back in 2018/2019 but it appeared in a much cleared way today: >> >> 1) the wiki.css file could offer more differentiation between headers (only >> 2px of difference in size is not very visible on modern screens) > > Can you try to modify the wiki.css? I gave admin permissions to brandelune, so > you can upload a modified version if it is OK for you. I can make a proposal. I've logged in to the Wiki interface but I'm not sure where I'd upload the modified file. >> 2) there does not seem to be a way to "name" internal parts so as to provide >> HTML anchors and link to internal parts of a document (like a "normal" ToC >> would do). > > Hmm, true ... That would be cool, but is way above what I can do in Picolisp :-) -- Jean-Christophe Helary @brandelune https://mac4translators.blogspot.com https://sr.ht/~brandelune/omegat-as-a-book/ -- UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe
Re: Wiki modifications
> I think I had that in mind when I made my first modifications to the wiki > back in 2018/2019 but it appeared in a much cleared way today: > > 1) the wiki.css file could offer more differentiation between headers (only > 2px of difference in size is not very visible on modern screens) Can you try to modify the wiki.css? I gave admin permissions to brandelune, so you can upload a modified version if it is OK for you. > 2) there does not seem to be a way to "name" internal parts so as to provide > HTML anchors and link to internal parts of a document (like a "normal" ToC > would do). Hmm, true ... ☺/ A!ex -- UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe
Re: Wiki modifications
Alex, I'm glad the modifs are ok. I think I had that in mind when I made my first modifications to the wiki back in 2018/2019 but it appeared in a much cleared way today: 1) the wiki.css file could offer more differentiation between headers (only 2px of difference in size is not very visible on modern screens) 2) there does not seem to be a way to "name" internal parts so as to provide HTML anchors and link to internal parts of a document (like a "normal" ToC would do). -- Jean-Christophe Helary @brandelune https://mac4translators.blogspot.com https://sr.ht/~brandelune/omegat-as-a-book/ -- UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe
Re: Wiki modifications
Hi Jean-Christophe, > 1) I changed the order of info in the "Wiki quickstart" to put the page > creation at the top > https://picolisp.com/wiki/?help Good idea. > 2) I added a ToC on the Wiki home > https://picolisp.com/wiki/?home Great! This is indeed very usful. I always missed an initial navigation aide. > 3) I added a link to an "alternative macos build procedure" on the Wiki home > https://picolisp.com/wiki/?home > > 4) I added an "Alternative repository install for macOS" page > https://picolisp.com/wiki/?alternativeMacOSRepository Perfect! Thanks a lot! ☺/ A!ex -- UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe
Re: Unable to log into wiki
Thanks Alex! Regards, Kashyap On Wed, Jan 8, 2020 at 7:44 AM Alexander Burger wrote: > Hi Kashyap, > > > you please reset the password for me? > > Sure, I send you a new one by mail, and you can change it again. > > ☺/ A!ex > > -- > UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe >
Re: Unable to log into wiki
Hi Kashyap, > you please reset the password for me? Sure, I send you a new one by mail, and you can change it again. ☺/ A!ex -- UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe
Unable to log into wiki
Hi Alex et al, I believe I had created an account on the wiki - ckkashyap ( ckkash...@gmail.com) - however I seem to have forgotten the password. Can you please reset the password for me? Regards, Kashyap
Re: Reset password on PicoLisp Wiki home?
On Sun, Mar 31, 2019 at 05:04:10PM -0400, r cs wrote: > How do I find out who has administrator role on the wiki? This is indeed not possible with the normal member role, as for accessing the user and role admin the administrator role is required. I do have administrator role. The best is if you enter the #picolisp IRC channel, and send me a new password in a direct message. I will set it, and you should change it to another one as soon as possible. If you cannot access IRC, please send me a personal mail with the new password and we proceed as above. ☺/ A!ex -- UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe
Re: Reset password on PicoLisp Wiki home?
How do I find out who has administrator role on the wiki? Thanks, rcs On Sat, Nov 24, 2018 at 2:53 PM Alexander Burger wrote: > Hi r cs, > > > Is there a way for a user to either retrieve their password or reset it > on > > the PicoLisp Wiki home? > > Retrieving it is not possible, as only the hash is stored. But you could > ask > anyone with Administrator role to set a new one, and then log in and > change it. > > ☺/ A!ex > > -- > UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe > -- *Níl aon tinteán mar do thinteán féin. *[Irish Gaelic] (There is no fireside like your own fireside.)
Re: Picolisp Wiki Markup Syntax page
On Thu, Jan 03, 2019 at 12:31:03AM +0900, Jean-Christophe Helary wrote: > I'm slightly modified the wiki markup syntax help page: > https://picolisp.com/wiki/?help > > I've tried to use the markup to describe itself. Surely the right way to do :) > I've found two implementation minor issues, one for the line breaks and one > for the CSS attribute use on arbitrary contents. Please take a look at the > document and tell me if there are any issues with it. To me it looks good, doesn't it? ☺/ A!ex -- UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe
Picolisp Wiki Markup Syntax page
I'm slightly modified the wiki markup syntax help page: https://picolisp.com/wiki/?help I've tried to use the markup to describe itself. I've found two implementation minor issues, one for the line breaks and one for the CSS attribute use on arbitrary contents. Please take a look at the document and tell me if there are any issues with it. Thank you in advance. Jean-Christophe Jean-Christophe Helary --- http://mac4translators.blogspot.com @brandelune -- UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe
Re: css bug in the wiki rendering for nested lists
On Wed, Jan 02, 2019 at 07:50:44PM +0900, Jean-Christophe Helary wrote: > I'm currently working on documenting the wiki source syntax *by* using the Cool! > wiki source syntax. I spent most of yesterday afternoon doing that. There was > this item that was not working and I found one minor glitch related to line > breaks and one major one related to applying arbitrary CSS to a given item. > Those two are implementation issues, so for not I'll just document the current > behavior and maybe I'll be able to propose changes to lib.l if you agree. Sure, nice! Thanks! :) ☺/ A!ex -- UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe
Re: css bug in the wiki rendering for nested lists
> On Jan 2, 2019, at 19:07, Alexander Burger wrote:
>
> On Wed, Jan 02, 2019 at 06:48:09PM +0900, Jean-Christophe Helary wrote:
>> I am not seeing the change here.
>>
>> Can you confirm that you changed
>>
>>>> #main > ul li {
>>
>> to
>>
>>>> #main > ul > li {
>
> Yes, I copy/pasted from your mail. A browser cache issue perhaps?
Indeed. I did not reload enough :)
Thank you. That works now.
I'm currently working on documenting the wiki source syntax *by* using the wiki
source syntax. I spent most of yesterday afternoon doing that. There was this
item that was not working and I found one minor glitch related to line breaks
and one major one related to applying arbitrary CSS to a given item. Those two
are implementation issues, so for not I'll just document the current behavior
and maybe I'll be able to propose changes to lib.l if you agree.
Cheers,
Jean-Christophe Helary
---
http://mac4translators.blogspot.com @brandelune
Re: css bug in the wiki rendering for nested lists
On Wed, Jan 02, 2019 at 06:48:09PM +0900, Jean-Christophe Helary wrote:
> I am not seeing the change here.
>
> Can you confirm that you changed
>
> >> #main > ul li {
>
> to
>
> >> #main > ul > li {
Yes, I copy/pasted from your mail. A browser cache issue perhaps?
☺/ A!ex
--
UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe
Re: css bug in the wiki rendering for nested lists
Alex,
I am not seeing the change here.
Can you confirm that you changed
>> #main > ul li {
to
>> #main > ul > li {
?
there should be a ">" between "ul" and "li".
Thank you.
Jean-Christophe
> On Jan 2, 2019, at 15:48, Alexander Burger wrote:
>
> On Tue, Jan 01, 2019 at 05:44:24PM +0900, Jean-Christophe Helary wrote:
>> It looks like the culprit is the wiki.css file (L86):
>>
>> #main > ul li {
>> list-style-type: square;
>> }
>>
>> That selector applies the "list-style-type: square;" to *all* elements
>> under a element (including nested elements).
>>
>> The correct syntax for the selector is:
>>
>> #main > ul > li {
>> list-style-type: square;
>> }
>
> I see, thanks!
>
> I don't know CSS well, all these changes were done by various people. But I
> gladly change wiki.css as you suggest.
>
> I installed it on picolisp.com. Can you check?
>
> ☺/ A!ex
>
> --
> UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe
Jean-Christophe Helary
---
http://mac4translators.blogspot.com @brandelune
Re: css bug in the wiki rendering for nested lists
On Tue, Jan 01, 2019 at 05:44:24PM +0900, Jean-Christophe Helary wrote:
> It looks like the culprit is the wiki.css file (L86):
>
> #main > ul li {
>list-style-type: square;
> }
>
> That selector applies the "list-style-type: square;" to *all* elements
> under a element (including nested elements).
>
> The correct syntax for the selector is:
>
> #main > ul > li {
>list-style-type: square;
> }
I see, thanks!
I don't know CSS well, all these changes were done by various people. But I
gladly change wiki.css as you suggest.
I installed it on picolisp.com. Can you check?
☺/ A!ex
--
UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe
css bug in the wiki rendering for nested lists
+{
-{item}
-{
*{-{nested item}
-{nested item}}}
-{item}}
renders normally the ordered/unordered nesting,
but
*{
-{item}
-{
+{-{nested item}
-{nested item}}}
-{item}}
sets all the items to be unordered list items.
Which is weird because the rendered html is correct:
item
nested item
nested item
item
It looks like the culprit is the wiki.css file (L86):
#main > ul li {
list-style-type: square;
}
That selector applies the "list-style-type: square;" to *all* elements
under a element (including nested elements).
The correct syntax for the selector is:
#main > ul > li {
list-style-type: square;
}
that way the style is only applied to the direct children of .
reference:
https://developer.mozilla.org/en-US/docs/Web/CSS/Descendant_combinator
https://developer.mozilla.org/en-US/docs/Web/CSS/Child_combinator
Jean-Christophe Helary
---
http://mac4translators.blogspot.com @brandelune
--
UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe
Reset password on PicoLisp Wiki home?
Is there a way for a user to either retrieve their password or reset it on the PicoLisp Wiki home? Thanks, rcs -- *Níl aon tinteán mar do thinteán féin. *[Irish Gaelic] (There is no fireside like your own fireside.)
Re: Repeated call to fill out the survey on changing the Wiki
Hi Mansur, Python, so much layers of >abstraction there, that makes me crazy after PicoLisp :) I am glad to hear it is not just me having the same feeling. :) > >On 07.07.2018 21:39, Arie van Wingerden wrote: >> Hi all, >> >> so far, 20 people have done the survey. Probably there are much more >> PicoLisp users around. >> >> Please take a few minutes to help PicoLisp promotion forward by >filling >> out the survey here: https://eSurv.org?s=MOIEMH_753ad7ff >> >> There are still 10 days left. After that we can show the results:) >> >> Thank you all! >> Arie > >-- >UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe -- UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe
Re: Repeated call to fill out the survey on changing the Wiki
I filled out the survey, sorry about taking so long :) I think this is a good initiative. Regards, Mattias Jean-Christophe Helary skrev: (8 juli 2018 01:44:28 CEST) > > >> On Jul 8, 2018, at 1:56, Johann-Tobias Schäg >wrote: >> >> That is just the decision for the content of a text file that can be >easily modified. > >Any text file can easily be modified. What matters is how an >organization lets people modify its text files. >Arle is doing a nice job with the documentation. That's a very >important part of what keeps an organization alive. > >Jean-Christophe Helary >--- >http://mac4translators.blogspot.com @brandelune -- UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe
Re: Repeated call to fill out the survey on changing the Wiki
> On Jul 8, 2018, at 1:56, Johann-Tobias Schäg wrote: > > That is just the decision for the content of a text file that can be easily > modified. Any text file can easily be modified. What matters is how an organization lets people modify its text files. Arle is doing a nice job with the documentation. That's a very important part of what keeps an organization alive. Jean-Christophe Helary --- http://mac4translators.blogspot.com @brandelune
Re: Repeated call to fill out the survey on changing the Wiki
I’m on this list because I’m interested in picolisp and appreciate gleaning insights like the pilog thread, but haven’t actually had time to really use picolisp, so responding to the survey seems inappropriate. I’ll also note that the Gallup organization reports a 7% response rate in their polls, so you’re doing well with over 10%. On Sat, Jul 7, 2018 at 1:27 PM Yiorgos [George] Adamopoulos < yiorgos.adamopou...@gmail.com> wrote: > Well there is the 1-9-90 pattern about community participation. With 193 > people on the list and 20 filling the survey, the pattern is observed. > > (I belong to the 90 Paarl of the pattern) > > On Sat, 7 Jul 2018 at 20:18, Alexander Burger wrote: > >> On Sat, Jul 07, 2018 at 06:56:07PM +0200, Johann-Tobias Schäg wrote: >> > i find your active pushing of this survey very uncommon in this >> community. I >> > think 20 people are much. >> >> Well, depends ... this list currently has 193 members. >> >> —Alex >> >> -- >> UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe >> > -- > keep raising the bar >
Re: Repeated call to fill out the survey on changing the Wiki
How many of those 193 did you talk to? Ursprüngliche Nachricht Von: a...@software-lab.de Gesendet: 7. Juli 2018 7:19 nachm. An: picolisp@software-lab.de Antworten: picolisp@software-lab.de Betreff: Re: Repeated call to fill out the survey on changing the Wiki On Sat, Jul 07, 2018 at 06:56:07PM +0200, Johann-Tobias Schäg wrote: > i find your active pushing of this survey very uncommon in this community. I > think 20 people are much. Well, depends ... this list currently has 193 members. —Alex -- UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe PԔ � )mX��� ��zV�u�.n7�
Re: Reminder on Wiki survey
done, voted On Sat, Jun 30, 2018 at 9:44 AM Joe Golden wrote: > Hey! Vote! It's simple and painless ;-) > > On Sat, Jun 30, 2018 at 04:01:50PM +0200, Manuel Cano wrote: > >Hi, > > > >Hey! Vote! I've did it some days ago. > > > > > >Kind regards, > >Manu > > > >2018-06-30 14:10 GMT+02:00 Arie van Wingerden : > > > >> Thanks! > >> > >> Op za 30 jun. 2018 om 13:59 schreef Timur Ismagilov : > >> > >>> I voted. Just letting you know. > >>> > >>> — bouncepaw > >>> > >>> > >>> Исходное сообщение > >>> От: Arie van Wingerden > >>> Дата: 30.06.2018 16:20 (GMT+05:00) > >>> Кому: picolisp@software-lab.de > >>> Тема: Reminder on Wiki survey > >>> > >>> Hi, > >>> > >>> we got 9 responses so far, but we guess there are a lot more > participants > >>> / lurkers in this mailing list. > >>> > >>> Please fill out the survey here if you haven't done that yet: > >>> https://esurv.org/?s=MOIEMH_753ad7ff > >>> > >>> Thanks to those who already did participate :) > >>> > >>> Best, > >>>Arie > >>> > >> > > -- > Joe Golden > > -- > UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe >
Re: Reminder on Wiki survey
Hey! Vote! It's simple and painless ;-) On Sat, Jun 30, 2018 at 04:01:50PM +0200, Manuel Cano wrote: Hi, Hey! Vote! I've did it some days ago. Kind regards, Manu 2018-06-30 14:10 GMT+02:00 Arie van Wingerden : Thanks! Op za 30 jun. 2018 om 13:59 schreef Timur Ismagilov : I voted. Just letting you know. — bouncepaw Исходное сообщение От: Arie van Wingerden Дата: 30.06.2018 16:20 (GMT+05:00) Кому: picolisp@software-lab.de Тема: Reminder on Wiki survey Hi, we got 9 responses so far, but we guess there are a lot more participants / lurkers in this mailing list. Please fill out the survey here if you haven't done that yet: https://esurv.org/?s=MOIEMH_753ad7ff Thanks to those who already did participate :) Best, Arie -- Joe Golden -- UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe
Re: Reminder on Wiki survey
Hi, Hey! Vote! I've did it some days ago. Kind regards, Manu 2018-06-30 14:10 GMT+02:00 Arie van Wingerden : > Thanks! > > Op za 30 jun. 2018 om 13:59 schreef Timur Ismagilov : > >> I voted. Just letting you know. >> >> — bouncepaw >> >> >> Исходное сообщение >> От: Arie van Wingerden >> Дата: 30.06.2018 16:20 (GMT+05:00) >> Кому: picolisp@software-lab.de >> Тема: Reminder on Wiki survey >> >> Hi, >> >> we got 9 responses so far, but we guess there are a lot more participants >> / lurkers in this mailing list. >> >> Please fill out the survey here if you haven't done that yet: >> https://esurv.org/?s=MOIEMH_753ad7ff >> >> Thanks to those who already did participate :) >> >> Best, >>Arie >> >
Re: Reminder on Wiki survey
Thanks! Op za 30 jun. 2018 om 13:59 schreef Timur Ismagilov : > I voted. Just letting you know. > > — bouncepaw > > > Исходное сообщение > От: Arie van Wingerden > Дата: 30.06.2018 16:20 (GMT+05:00) > Кому: picolisp@software-lab.de > Тема: Reminder on Wiki survey > > Hi, > > we got 9 responses so far, but we guess there are a lot more participants > / lurkers in this mailing list. > > Please fill out the survey here if you haven't done that yet: > https://esurv.org/?s=MOIEMH_753ad7ff > > Thanks to those who already did participate :) > > Best, >Arie >
RE: Reminder on Wiki survey
I voted. Just letting you know. — bouncepaw Исходное сообщение От: Arie van Wingerden Дата: 30.06.2018 16:20 (GMT+05:00) Кому: picolisp@software-lab.de Тема: Reminder on Wiki survey Hi, we got 9 responses so far, but we guess there are a lot more participants / lurkers in this mailing list. Please fill out the survey here if you haven't done that yet: https://esurv.org/?s=MOIEMH_753ad7ff Thanks to those who already did participate :) Best, Arie
Reminder on Wiki survey
Hi, we got 9 responses so far, but we guess there are a lot more participants / lurkers in this mailing list. Please fill out the survey here if you haven't done that yet: https://esurv.org/?s=MOIEMH_753ad7ff Thanks to those who already did participate :) Best, Arie
Re: Wiki progress update ...
Hi Nehal, Op ma 25 jun. 2018 om 13:29 schreef Nehal : > While observing new changes made in picolisp wiki css, I observed on > https://picolisp.com/wiki/?PCE: > > 1. *Numbering* error of headings. 3 comes after 4 again! > Corrected. 2. "On Rosettacode you can find a wealth of examples on a huge *scala* of common programming problems." Perhaps you wanted to write 'scale'. Right. I changed it to range, which might be even a bit better. You may like to correct above minor changes. :) Yes, of course! Thank you. Best, Arie
Re: Wiki progress update ...
Thx. Manuel! Op ma 25 jun. 2018 om 14:09 schreef Manuel Cano : > Hi, > > I've corrected the missing quote: ...known "Perl Cookbook. > > :) > > > Kind regards, > Manu > > 2018-06-01 17:19 GMT+02:00 Arie van Wingerden : > >> The first section of PLEAC (Strings) is now at about 76% ready >> >> Some examples are rewritten a little, in order to make it easier for >> people to just copy and paste the code to see what happens. >> >> I took great effort to verify each and every example. >> >> Also I added a reference to all used functions per example, so the user >> can easily switch back and forth. >> >> If anybody would be so kind to have a look and check if everything is OK >> overall...? >> >> Any input is welcome. But, beware that the Wiki markup is really simple >> (in the spirit of PicoLisp itself) so, not everything is possible (I >> think?). >> >> /Arie >> > >
Re: Wiki progress update ...
Hi, I've corrected the missing quote: ...known "Perl Cookbook. :) Kind regards, Manu 2018-06-01 17:19 GMT+02:00 Arie van Wingerden : > The first section of PLEAC (Strings) is now at about 76% ready > > Some examples are rewritten a little, in order to make it easier for > people to just copy and paste the code to see what happens. > > I took great effort to verify each and every example. > > Also I added a reference to all used functions per example, so the user > can easily switch back and forth. > > If anybody would be so kind to have a look and check if everything is OK > overall...? > > Any input is welcome. But, beware that the Wiki markup is really simple > (in the spirit of PicoLisp itself) so, not everything is possible (I > think?). > > /Arie >
Re: Wiki progress update ...
Hi Arie, While observing new changes made in picolisp wiki css, I observed on https://picolisp.com/wiki/?PCE: 1. *Numbering* error of headings. 3 comes after 4 again! 2. "On Rosettacode you can find a wealth of examples on a huge *scala* of common programming problems." Perhaps you wanted to write 'scale'. You may like to correct above minor changes. :) Best, Nehal On 6/2/18, Arie van Wingerden wrote: > Hi Alex, > > thx. for taking time to check!!! > > I corrected those points you mention. > > Thx. to you too :) > > Because I now just try to do this stuff fast, I only have a bit of time to > look at functions in more detail. > I really am impressed by the many useful functions. > > Also nice that strings and symbols are somewhat unified. This is unique in > the Lisp world I think? > > Already noticed I have to thoroughly go through the "numbers", especially > for the "emulated" fixed point numbers. > > Keep up the good work, >Arie > > 2018-06-02 14:50 GMT+02:00 Alexander Burger : > >> Hi Arie, >> >> > The first section of PLEAC (Strings) is now at about 76% ready. >> > ... >> > Some examples are rewritten a little, in order to make it easier for >> people >> > to just copy and paste the code to see what happens. >> > >> > I took great effort to verify each and every example. >> >> Pefect! Indeed a *lot* of work. >> >> >> > Also I added a reference to all used functions per example, so the user >> can >> > easily switch back and forth. >> >> A very good idea! This makes it very easy to follow the examples. >> >> >> > If anybody would be so kind to have a look and check if everything is >> > OK >> > overall...? >> >> I found a few minor issues: >> >>— The first example of "Expanding and Compressing Tabs" says "Note >> that >> the >> 'line' function reads a line from STDIN". This is true here (i.e. in >> a >> REPL), but for the general case I would recommend to write "... >> reads >> a >> line from the current input channel". >> >>— In "Escaping Characters" the variable should be 'CharList' (upper >> case 'L') >> >> Many thanks! >> ♪♫ Alex >> >> -- >> UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe >> >
Re: Wiki css
Hi, I think something like Picolisp wiki has to be clear and easy to read, not necessarily (althought it is for me) "pretty", but practical. Don't be picky. The only thing I don't really like is to have code in bold. (We don't code in bold!) But even if I don't really like it, I find making code outstanding from the rest of the text make it easier to look at the code and avoid distraction. As for the "real state", I find it easier to read short lines. I get lost when reading very long lines when it comes to go back (CRLF :-) to the beginning of next line. (And I know it happens to many people, that's exactly why they do that in blogs and articles.) It is now very clear and easy to read for me. So thanks Arie. Kind regards, Manu 2018-06-25 11:41 GMT+02:00 Arie van Wingerden : > Hi Manuel, > > I like as it is now. Ari has made a good job, don't throw it away. > > Pffft. I really thought it was all bad news. Thx. > > If it was hard for someone before, they could have done what Ari has made
Re: Wiki css
Hi Jean-Christophe, Op ma 25 jun. 2018 om 12:04 schreef Jean-Christophe Helary < brandel...@gmail.com>: I agree. But it is always difficult to discuss a proposal before seeing > some kind of implementation. > Right. Thtat's a thing I really need to change.! > I think it is possible to further improve Arie's work by laying out a few > design principles, like for example not add decorations that do not have a > clear function (i.e. usually italics and bold are kept to show a > contrasting emphasis within a text). That's usually the main issue with > heavily decorated documents (I'm not saying that this page is heavily > decorated :). > In fact I disliked the HUGE headers and wanted them a bit smaller .. :) T hx. Arie
Re: Wiki css
No problem :) Op ma 25 jun. 2018 om 12:04 schreef Manuel Cano : > Hi Arie, > > Sorry. I've mistyped you name! > > > Kind regards, > Manu > > 2018-06-25 11:41 GMT+02:00 Arie van Wingerden : > > > Hi Manuel, > > > > I like as it is now. Ari has made a good job, don't throw it away. > > > > Pffft. I really thought it was all bad news. Thx. > > > > If it was hard for someone before, they could have done what Ari has made
Re: Wiki css
Hi Arie, Sorry. I've mistyped you name! Kind regards, Manu 2018-06-25 11:41 GMT+02:00 Arie van Wingerden : > Hi Manuel, > > I like as it is now. Ari has made a good job, don't throw it away. > > Pffft. I really thought it was all bad news. Thx. > > If it was hard for someone before, they could have done what Ari has made
Re: Wiki css
> On Jun 25, 2018, at 18:03, Manuel Cano wrote: > > Hi all, > > I like as it is now. Ari has made a good job, don't throw it away. > If it was hard for someone before, they could have done what Ari has made. I agree. But it is always difficult to discuss a proposal before seeing some kind of implementation. I think it is possible to further improve Arie's work by laying out a few design principles, like for example not add decorations that do not have a clear function (i.e. usually italics and bold are kept to show a contrasting emphasis within a text). That's usually the main issue with heavily decorated documents (I'm not saying that this page is heavily decorated :). Jean-Christophe -- UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe
Re: Wiki css
Hi Johann, I would also keep it > ... > OK. You don't like the updates I guess. > > and somebody finds something annoying (like italic > headlines) they should just send an "upgraded" css to the mailing list and > have some people try it out. > It indeed would be nice *if* people did such thing. But I guess it would result in the same kind of personal taste issues, even preventing to put any changes life at all. At any time there would be people not liking specific things. Thx. Arie
Re: Wiki css
I would also keep it and somebody finds something annoying (like italic headlines) they should just send an "upgraded" css to the mailing list and have some people try it out. 2018-06-25 11:03 GMT+02:00 Manuel Cano : > Hi all, > > I like as it is now. Ari has made a good job, don't throw it away. > If it was hard for someone before, they could have done what Ari has made
Re: Wiki css
Hi Manuel, I like as it is now. Ari has made a good job, don't throw it away. Pffft. I really thought it was all bad news. Thx. If it was hard for someone before, they could have done what Ari has made. That's right. But it is *really* difficult to do things that everybody likes ... Thx! Arie
Re: Wiki css
Hi Alex, might be a good Idea. But the mailing list and IRC don't seem to be really appropriate to do voting. Does somebody know if there is a good free online possibility out there to do voting on several things in one go? If so, I am surely willing to take the effort and follow up democratically! Will try to find this myself as well. Thanks! Arie Op ma 25 jun. 2018 om 11:00 schreef Alexander Burger : > Hi all, > > > after reading a few reactions and also my struggle to get things right > (in > > *my* opinion), I realize that it really is impossible to please > everybody. > > > > Given the fact that also I seem to be the only person not liking the old > > CSS and that the new CSS is a "regression" it is much better to restore > the > > old CSS. > > > > My only purpose is to make the Wiki *more* attractive and not to make it > > *worse*. > > > > @AlexB > > To not further disturb the community I'd like Alex to restore the > previous > > CSS (which I also attach here). > > Really a tough decision ... How about some democratic process? > > What if anybody concerned about the matter votes here (or in IRC, or in > the Wiki > itself?) within the next week, and we do the final decision based on that? > > ♪♫ Alex > > -- > UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe >
Re: Wiki css
Hi all, I like as it is now. Ari has made a good job, don't throw it away. If it was hard for someone before, they could have done what Ari has made. Kind regards, Manuel El lun., 25 jun. 2018 11:00, Alexander Burger escribió: > Hi all, > > > after reading a few reactions and also my struggle to get things right > (in > > *my* opinion), I realize that it really is impossible to please > everybody. > > > > Given the fact that also I seem to be the only person not liking the old > > CSS and that the new CSS is a "regression" it is much better to restore > the > > old CSS. > > > > My only purpose is to make the Wiki *more* attractive and not to make it > > *worse*. > > > > @AlexB > > To not further disturb the community I'd like Alex to restore the > previous > > CSS (which I also attach here). > > Really a tough decision ... How about some democratic process? > > What if anybody concerned about the matter votes here (or in IRC, or in > the Wiki > itself?) within the next week, and we do the final decision based on that? > > ♪♫ Alex > > -- > UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe >
Re: Wiki css
Hi all, > after reading a few reactions and also my struggle to get things right (in > *my* opinion), I realize that it really is impossible to please everybody. > > Given the fact that also I seem to be the only person not liking the old > CSS and that the new CSS is a "regression" it is much better to restore the > old CSS. > > My only purpose is to make the Wiki *more* attractive and not to make it > *worse*. > > @AlexB > To not further disturb the community I'd like Alex to restore the previous > CSS (which I also attach here). Really a tough decision ... How about some democratic process? What if anybody concerned about the matter votes here (or in IRC, or in the Wiki itself?) within the next week, and we do the final decision based on that? ♪♫ Alex -- UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe
Re: Wiki - asking for last calls on fonts etc.
Hi Arie, > - don't limit the page to use 60% of the browser window, it's a waste > > of real-estate (too much whitespace on left/right). That technique > > should be reserved for blogs/articles. > > > > Well, that choice was made long ago by Alexander Burger himself. Nothing > has changed. Well, just for the records, that was actually not me but Erik Gustafson, who made the last big rewrite of the Wiki. In fact, I'm usually not concerned about style issues at all, as I do all browsing in a plain text browser (w3m). ♪♫ Alex -- UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe
Wiki css
Hi all,
after reading a few reactions and also my struggle to get things right (in
*my* opinion), I realize that it really is impossible to please everybody.
Given the fact that also I seem to be the only person not liking the old
CSS and that the new CSS is a "regression" it is much better to restore the
old CSS.
My only purpose is to make the Wiki *more* attractive and not to make it
*worse*.
@AlexB
To not further disturb the community I'd like Alex to restore the previous
CSS (which I also attach here).
BTW. no hard feelings to commenters. I hear you :)
Best wishes to all,
Arie
/* 26apr18edg
* 07aug13abu
* 30jan12jk
* (c) Software Lab. Alexander Burger
*/
/*/
/* Utils */
.left {float: left}
.right {float: right}
.clr{clear: both}
.norm {text-align: left}
.align {text-align: right}
.center {text-align: center}
.black {color: black}
.red{color: red}
.green {color: green}
.blue {color: blue}
.bold {font-weight: bold}
.mono {font-family: monospace}
/***/
/* Simple responsive container */
.container {
position: relative;
width: 86%;
display: block;
margin: 0 auto;
box-sizing: border-box;
}
@media screen and (min-width: 900px) {
.container {
max-width: 768px;
}
}
//
/* Defaults */
fieldset {
padding: 0.3em 0.4em 0.7em 0.8em; /* ie */
}
input, textarea, select {
font-size: smaller;
background-color: #eee;
}
body {
margin: 0;
font-family: 'Open Sans', sans-serif;
}
/**/
/* Headers/typography */
h1, h2, h3, h4, h5, h6 {
font-family: 'Exo';
color: #222554;
font-weight: 800;
letter-spacing: -1px;
margin-bottom: 2rem;
}
h5, h6 {
color: #bbbedd;
font-weight: 500;
}
/* adapted from skeleton.css */
h1 { font-size: 3.4rem; line-height: 1.2; }
h2 { font-size: 3.0rem; line-height: 1.25; }
h3 { font-size: 2.6rem; line-height: 1.3; }
h4 { font-size: 2.2rem; line-height: 1.35; }
h5 { font-size: 1.8rem; line-height: 1.5; }
h6 { font-size: 1.4rem; line-height: 1.6; margin-top: 0; }
/**/
/* Wiki document body */
#main {
font-size: 16px;
font-weight: 300;
color: #333;
}
p {
margin-top: 0; }
/* List styles */
#main > ul li {
list-style-type: square;
}
#main li {
margin-bottom: 8px;
}
#main img {
max-width: 100%;
height: auto;
}
/* Links */
a {
color: #6067af;
font-weight: 400;
text-decoration: none;
}
a:hover,
a:focus {
color: #6dc066;
text-decoration: underline;
}
/* Larger fonts for larger screens */
@media screen and (min-width: 900px) {
#main { font-size: 18px; }
h1 { font-size: 3.6rem; }
h2 { font-size: 3.2rem; }
h3 { font-size: 2.8rem; }
h4 { font-size: 2.4rem; }
h5 { font-size: 2.0rem; }
h6 { font-size: 1.6rem; }
}
//
/* Menu */
#menu {
background: #090910;
width: 100%;
margin-bottom: 64px;
display: flex;
display: -webkit-flex;
flex-wrap: wrap;
-webkit-flex-wrap: wrap;
align-items: center;
-webkit-align-items: center;
justify-content: space-around;
-webkit-justify-content: space-around;
}
/* Logo (homepage link) */
#menu a img {
max-width: 100%;
height: auto;
padding: 12px;
}
/* Menu links */
#menu a {
color: #8c8faf;
text-decoration: none;
text-transform: uppercase;
}
#menu a:hover,
#menu a:focus {
color: #6dc066;
border: none;
}
/* Remove phantom margin/padding */
#menu ul {
margin: initial;
padding: initial;
}
#menu ul li {
list-style: none;
margin: 12px;
padding: none;
}
#menuLogin a {
margin: 12px;
}
/* display "Downloads Documentation Community" inline
* on larger screens */
@media screen and (min-width: 1000px) {
#menu ul {
display: inline-flex;
}
}
/****/
/* Wiki text search */
#searchGrp {
margin: 8px;
}
#searchGrp form {
margin: 0;
}
#searchGrp input,
#searchGrp .submit {
border-radius: 1px;
padding: 4px;
margin: 4px;
}
#searchGrp input {
background-color: white;
border: 2px solid white;
}
#searchGrp .submit {
background-color: #090910;
border: 2px solid #8c8faf;
color: #8c8faf;
text-transform: uppercase;
}
#searchGrp .submit:hover {
border-color: #6dc066;
color: #6dc066;
}
#searchGrp .submit:active {
color: #090910;
background-color: #6dc066;
}
/* Search Results */
#searchGrp strong {
color: #6dc066; /* PL green */
}
#searchGrp strong,
#searchGrp a {
margin-left: 22px;
text-transform: none;
}
/* Make search pretty on large screens */
@media screen and (min-width: 1400px) {
#searchGrp {
max-height: 66px;
max-width: 300px;
}
/* darker links against white bg */
#searchGrp a {
color: #6067af;
}
}
#expires {
position: absolute;
top: 8px;
right: 44px;
color: #f05658;
font-size: small;
}
/* Code highlighting */
.code {
color: black;
font-size: smaller;
Re: Wiki - asking for last calls on fonts etc.
Hi Nehal, I see.Well, my biggest wish is to add more useful content than changing the layout. For me personally, the layout wasn't so nice. Guessing that this would be the case for other people, I started to try to help. Maybe we should wait for a while for all reactions. Ultimate choice could be to restore the "old" CSS. Thanks for commenting. Best, Arie Op ma 25 jun. 2018 om 07:20 schreef Nehal : > I agree with Alexander. Base font would be better if bigger as before. I > don't have much issue with look and feel of italicized content but base > text be bigger (also with bigger base text italics may have to redefined)
Re: Wiki - asking for last calls on fonts etc.
Hi Alexander, I haven't been following the recent website changes, but right now it > seems the picolisp.com website is much worse than it used to be. A > regression. > Well, that is a blow to take in ... > - text is too small. Please use browser relative sizes in "em" and "%" > instead of "px". > OK. Good. > - don't put code samples in "bold". This is very hard to read. > Maybe for some people, but for people with worse vision that might be completely different. > - don't use italics for headers and section headers. > That really is a question of "taste" I think! Isn't it? > - code samples background colour fights with text. bg should be much > lighter. > Weird. It is the same background color as ever ... - don't use black #000 for text, but something a bit lighter like #222 > or #333. > Again, I know for a fact that visually impaired people *hate* vague letters. What is so bad? - don't limit the page to use 60% of the browser window, it's a waste > of real-estate (too much whitespace on left/right). That technique > should be reserved for blogs/articles. > Well, that choice was made long ago by Alexander Burger himself. Nothing has changed. > I'm not a designer, but I think the above is common sense. > I'm not a designer as well. For me the changes seem an improvement
Re: Wiki - asking for last calls on fonts etc.
I agree with Alexander. Base font would be better if bigger as before. I don't have much issue with look and feel of italicized content but base text be bigger (also with bigger base text italics may have to redefined). The earlier wiki settings were also great and only some categorization of articles was required. I got extremely occupied in other things and couldn't focus on organization in last months here however it was well placed in my mind. With further suggestions from Mr Burger, I think we should focus on giving quality articles that are well managed and organized. Fonts, look and presence were great even before. I have also not followed this discussion closely. So if this is being done with collective decision making then it may be ok to continue with improvements. I'll be happy to contribute in any way I can. :) Regards, Nehal सा विद्या या विमुक्तये On Mon, Jun 25, 2018, 7:10 AM Alexander Williams wrote: > Hello, > > I haven't been following the recent website changes, but right now it > seems the picolisp.com website is much worse than it used to be. A > regression. > > A few issues I noted: > > - text is too small. Please use browser relative sizes in "em" and "%" > instead of "px". > > - don't put code samples in "bold". This is very hard to read. > > - don't use italics for headers and section headers. > > - code samples background colour fights with text. bg should be much > lighter. > > - don't use black #000 for text, but something a bit lighter like #222 > or #333. > > - don't limit the page to use 60% of the browser window, it's a waste > of real-estate (too much whitespace on left/right). That technique > should be reserved for blogs/articles. > > I'm not a designer, but I think the above is common sense. > > Cheers, > > > AW > >
Re: Wiki - asking for last calls on fonts etc.
Hello, I haven't been following the recent website changes, but right now it seems the picolisp.com website is much worse than it used to be. A regression. A few issues I noted: - text is too small. Please use browser relative sizes in "em" and "%" instead of "px". - don't put code samples in "bold". This is very hard to read. - don't use italics for headers and section headers. - code samples background colour fights with text. bg should be much lighter. - don't use black #000 for text, but something a bit lighter like #222 or #333. - don't limit the page to use 60% of the browser window, it's a waste of real-estate (too much whitespace on left/right). That technique should be reserved for blogs/articles. I'm not a designer, but I think the above is common sense. Cheers, AW signature.asc Description: OpenPGP digital signature
Re: Wiki updated fonts etc.
> On Jun 25, 2018, at 0:02, Arie van Wingerden wrote: > > OK. Thx! > I'll check on mark-up later then! I mean that it's not that important to me. :) Don't worry :) > Best, > Arie > > Op zo 24 jun. 2018 om 13:31 schreef Jean-Christophe Helary > mailto:brandel...@gmail.com>>: > Ok, I won't touch the css but I've removed the ":" at the beginning of 2 > lines of code and I added the macOS text. Jean-Christophe
Re: Wiki updated fonts etc.
OK. Thx!
I'll check on mark-up later then!
Best,
Arie
Op zo 24 jun. 2018 om 13:31 schreef Jean-Christophe Helary <
brandel...@gmail.com>:
> Ok, I won't touch the css but I've removed the ":" at the beginning of 2
> lines of code and I added the macOS text.
>
> JC
>
> On Jun 24, 2018, at 18:32, Arie van Wingerden wrote:
>
> Hi Jean-Christophe,
>
> thanks for the feedback!
>
> Would you be so kind to update these things yourself?
>
> It is quite impossible to forsee every wish. I just tried :)
>
> If you remove bold from code, would you please have a look at the headers
> h1..h6.
>
> Before the headers were awkwardly big. I tried to change that a bit.
>
> Also I made them italic for even numbered headers. When showing all of
> them in a page, it still is a bit awkward I do like the italic ones. Maybe
> they should be italic alltogether?
>
> Please be aware that they have different specs for bigger screens ...
>
> Please have a look!
>
> I am looking forward to concentrate on PicoLisp (examples) itself :)
>
> Many thx!
>Arie
>
> Op zo 24 jun. 2018 03:54 schreef Jean-Christophe Helary <
> brandel...@gmail.com>:
>
>> Nice job. :)
>>
>> I have just a few comments:
>> 1) I liked the tongue-in-cheek tone of the top page with : Picolisp can
>> do... Numbers !!! etc. The serious version of the current page makes
>> picolisp look like any other lisp...
>> 2) I don't think the bold font for code is a good idea but I don't
>> remember if it was like this before or not
>> 3) The examples display some differences. Some start with : some not,
>> etc. I can fix that if that's OK.
>>
>> Also, there should be a reference to macOS in the Install section,
>> something like:
>>
>> 4{Install on Linux}
>> You came here to play with another programming language, right?
>> If you're using a Debian-based Linux (like
>> Ubuntu or Mint), simply install it with:
>> :{
>>$ sudo apt-get install picolisp
>> }
>> and check out the ^{https://software-lab.de/doc/tut.html tutorial}.
>>
>> Otherwise, grab the latest version -
>> ^{https://software-lab.de/picoLisp.tgz [picoLisp.tgz]} - unpack it,
>> follow the
>> instructions from the ^{https://software-lab.de/INSTALL INSTALL} file,
>> and /{then} check out the ^{https://software-lab.de/doc/tut.html
>> tutorial}.
>> 4{Install on Windows Sybsystem for Linux (WSL)}
>> See here: ={WSL Install PicoLisp on Windows 10}
>> 4{Install on macOS}
>> It is not possible to install picolisp on macOS, or even to build it
>> without significant modifications to the code. The easiest way to access it
>> on your machine is to install it on a lightweight Linux system and to ssh
>> to it.
>>
>> JC
>>
>> On Jun 24, 2018, at 1:46, Arie van Wingerden wrote:
>>
>> Hi all,
>>
>> today the CSS for the Wiki has been updated.
>>
>> It is really difficult to find appropriate fonts, font-sizes and -colors.
>>
>> 1. menu now has bright white letters, which is better for people having
>> difficulty with reading
>>
>> 2. headers are a bit smaller, but maybe they need a bit of adjustment
>> still
>>
>> I already updated the:
>>- Wiki home
>>- Wiki documentation
>>- Wiki collection of examples
>>- all underlying PLEAC example pages
>> to optimally use the new layout.
>>
>> I hope this will work for most people. If not, feel free to contact me or
>> make changes yourself :)
>>
>> What is not yet done is what Karl-Heinz suggested. I think that is more a
>> PicoLisp code thing that generates HTML. @Karl-Heinz: could you look into
>> that?
>>
>> I'll try to update other pages to better match the changed possibilities
>> as well.
>>
>> BTW I'll try and use the mailing list only for this kind of announcements
>> to avoid clutter. Since I am a dinosaur I was not aware that much :)
>>
>> Best,
>>Arie
>>
>>
>> Jean-Christophe Helary
>> ---
>> http://mac4translators.blogspot.com @brandelune
>>
>>
>>
> Jean-Christophe Helary
> ---
> http://mac4translators.blogspot.com @brandelune
>
>
>
New page in Wiki
Hi, under "Start here" on this page https://picolisp.com/wiki/?documentation I added a page called "The pros and cons of PicoLisp". This is a more concise version of the current Tractatus Pico-Blaesicus, which currently is still used as a demo for saerving web pages and paragraph folding. I intend to change that demo to more general stuff. The reason for that is that people might think that the current demo *is* the official PicoLisp documentation, which can be misleading. Feel free to correct any errors :) Best, Arie
Re: Wiki updated fonts etc.
Ok, I won't touch the css but I've removed the ":" at the beginning of 2 lines
of code and I added the macOS text.
JC
> On Jun 24, 2018, at 18:32, Arie van Wingerden wrote:
>
> Hi Jean-Christophe,
>
> thanks for the feedback!
>
> Would you be so kind to update these things yourself?
>
> It is quite impossible to forsee every wish. I just tried :)
>
> If you remove bold from code, would you please have a look at the headers
> h1..h6.
>
> Before the headers were awkwardly big. I tried to change that a bit.
>
> Also I made them italic for even numbered headers. When showing all of them
> in a page, it still is a bit awkward I do like the italic ones. Maybe they
> should be italic alltogether?
>
> Please be aware that they have different specs for bigger screens ...
>
> Please have a look!
>
> I am looking forward to concentrate on PicoLisp (examples) itself :)
>
> Many thx!
>Arie
>
> Op zo 24 jun. 2018 03:54 schreef Jean-Christophe Helary <mailto:brandel...@gmail.com>>:
> Nice job. :)
>
> I have just a few comments:
> 1) I liked the tongue-in-cheek tone of the top page with : Picolisp can do...
> Numbers !!! etc. The serious version of the current page makes picolisp look
> like any other lisp...
> 2) I don't think the bold font for code is a good idea but I don't remember
> if it was like this before or not
> 3) The examples display some differences. Some start with : some not, etc. I
> can fix that if that's OK.
>
> Also, there should be a reference to macOS in the Install section, something
> like:
>
> 4{Install on Linux}
> You came here to play with another programming language, right?
> If you're using a Debian-based Linux (like
> Ubuntu or Mint), simply install it with:
> :{
>$ sudo apt-get install picolisp
> }
> and check out the ^{https://software-lab.de/doc/tut.html
> <https://software-lab.de/doc/tut.html> tutorial}.
>
> Otherwise, grab the latest version -
> ^{https://software-lab.de/picoLisp.tgz <https://software-lab.de/picoLisp.tgz>
> [picoLisp.tgz]} - unpack it, follow the
> instructions from the ^{https://software-lab.de/INSTALL
> <https://software-lab.de/INSTALL> INSTALL} file,
> and /{then} check out the ^{https://software-lab.de/doc/tut.html
> <https://software-lab.de/doc/tut.html> tutorial}.
> 4{Install on Windows Sybsystem for Linux (WSL)}
> See here: ={WSL Install PicoLisp on Windows 10}
> 4{Install on macOS}
> It is not possible to install picolisp on macOS, or even to build it without
> significant modifications to the code. The easiest way to access it on your
> machine is to install it on a lightweight Linux system and to ssh to it.
>
> JC
>
>> On Jun 24, 2018, at 1:46, Arie van Wingerden > <mailto:xapw...@gmail.com>> wrote:
>>
>> Hi all,
>>
>> today the CSS for the Wiki has been updated.
>>
>> It is really difficult to find appropriate fonts, font-sizes and -colors.
>>
>> 1. menu now has bright white letters, which is better for people having
>> difficulty with reading
>>
>> 2. headers are a bit smaller, but maybe they need a bit of adjustment still
>>
>> I already updated the:
>>- Wiki home
>>- Wiki documentation
>>- Wiki collection of examples
>>- all underlying PLEAC example pages
>> to optimally use the new layout.
>>
>> I hope this will work for most people. If not, feel free to contact me or
>> make changes yourself :)
>>
>> What is not yet done is what Karl-Heinz suggested. I think that is more a
>> PicoLisp code thing that generates HTML. @Karl-Heinz: could you look into
>> that?
>>
>> I'll try to update other pages to better match the changed possibilities as
>> well.
>>
>> BTW I'll try and use the mailing list only for this kind of announcements to
>> avoid clutter. Since I am a dinosaur I was not aware that much :)
>>
>> Best,
>>Arie
>
> Jean-Christophe Helary
> ---
> http://mac4translators.blogspot.com <http://mac4translators.blogspot.com/>
> @brandelune
>
>
Jean-Christophe Helary
---
http://mac4translators.blogspot.com @brandelune
Re: Wiki updated fonts etc.
Hi Jean-Christophe,
thanks for the feedback!
Would you be so kind to update these things yourself?
It is quite impossible to forsee every wish. I just tried :)
If you remove bold from code, would you please have a look at the headers
h1..h6.
Before the headers were awkwardly big. I tried to change that a bit.
Also I made them italic for even numbered headers. When showing all of them
in a page, it still is a bit awkward. I do like the italic ones. Maybe they
should be italic alltogether?
Please be aware that they have different specs for bigger screens ...
Please have a look!
I am looking forward to concentrate on PicoLisp (examples) itself :)
Many thx!
Arie
Op zo 24 jun. 2018 03:54 schreef Jean-Christophe Helary <
brandel...@gmail.com>:
> Nice job. :)
>
> I have just a few comments:
> 1) I liked the tongue-in-cheek tone of the top page with : Picolisp can
> do... Numbers !!! etc. The serious version of the current page makes
> picolisp look like any other lisp...
> 2) I don't think the bold font for code is a good idea but I don't
> remember if it was like this before or not
> 3) The examples display some differences. Some start with : some not, etc.
> I can fix that if that's OK.
>
> Also, there should be a reference to macOS in the Install section,
> something like:
>
> 4{Install on Linux}
> You came here to play with another programming language, right?
> If you're using a Debian-based Linux (like
> Ubuntu or Mint), simply install it with:
> :{
>$ sudo apt-get install picolisp
> }
> and check out the ^{https://software-lab.de/doc/tut.html tutorial}.
>
> Otherwise, grab the latest version -
> ^{https://software-lab.de/picoLisp.tgz [picoLisp.tgz]} - unpack it,
> follow the
> instructions from the ^{https://software-lab.de/INSTALL INSTALL} file,
> and /{then} check out the ^{https://software-lab.de/doc/tut.html
> tutorial}.
> 4{Install on Windows Sybsystem for Linux (WSL)}
> See here: ={WSL Install PicoLisp on Windows 10}
> 4{Install on macOS}
> It is not possible to install picolisp on macOS, or even to build it
> without significant modifications to the code. The easiest way to access it
> on your machine is to install it on a lightweight Linux system and to ssh
> to it.
>
> JC
>
> On Jun 24, 2018, at 1:46, Arie van Wingerden wrote:
>
> Hi all,
>
> today the CSS for the Wiki has been updated.
>
> It is really difficult to find appropriate fonts, font-sizes and -colors.
>
> 1. menu now has bright white letters, which is better for people having
> difficulty with reading
>
> 2. headers are a bit smaller, but maybe they need a bit of adjustment still
>
> I already updated the:
>- Wiki home
>- Wiki documentation
>- Wiki collection of examples
>- all underlying PLEAC example pages
> to optimally use the new layout.
>
> I hope this will work for most people. If not, feel free to contact me or
> make changes yourself :)
>
> What is not yet done is what Karl-Heinz suggested. I think that is more a
> PicoLisp code thing that generates HTML. @Karl-Heinz: could you look into
> that?
>
> I'll try to update other pages to better match the changed possibilities
> as well.
>
> BTW I'll try and use the mailing list only for this kind of announcements
> to avoid clutter. Since I am a dinosaur I was not aware that much :)
>
> Best,
>Arie
>
>
> Jean-Christophe Helary
> ---
> http://mac4translators.blogspot.com @brandelune
>
>
>
Re: Wiki updated fonts etc.
Nice job. :)
I have just a few comments:
1) I liked the tongue-in-cheek tone of the top page with : Picolisp can do...
Numbers !!! etc. The serious version of the current page makes picolisp look
like any other lisp...
2) I don't think the bold font for code is a good idea but I don't remember if
it was like this before or not
3) The examples display some differences. Some start with : some not, etc. I
can fix that if that's OK.
Also, there should be a reference to macOS in the Install section, something
like:
4{Install on Linux}
You came here to play with another programming language, right?
If you're using a Debian-based Linux (like
Ubuntu or Mint), simply install it with:
:{
$ sudo apt-get install picolisp
}
and check out the ^{https://software-lab.de/doc/tut.html tutorial}.
Otherwise, grab the latest version -
^{https://software-lab.de/picoLisp.tgz [picoLisp.tgz]} - unpack it, follow the
instructions from the ^{https://software-lab.de/INSTALL INSTALL} file,
and /{then} check out the ^{https://software-lab.de/doc/tut.html tutorial}.
4{Install on Windows Sybsystem for Linux (WSL)}
See here: ={WSL Install PicoLisp on Windows 10}
4{Install on macOS}
It is not possible to install picolisp on macOS, or even to build it without
significant modifications to the code. The easiest way to access it on your
machine is to install it on a lightweight Linux system and to ssh to it.
JC
> On Jun 24, 2018, at 1:46, Arie van Wingerden wrote:
>
> Hi all,
>
> today the CSS for the Wiki has been updated.
>
> It is really difficult to find appropriate fonts, font-sizes and -colors.
>
> 1. menu now has bright white letters, which is better for people having
> difficulty with reading
>
> 2. headers are a bit smaller, but maybe they need a bit of adjustment still
>
> I already updated the:
>- Wiki home
>- Wiki documentation
>- Wiki collection of examples
>- all underlying PLEAC example pages
> to optimally use the new layout.
>
> I hope this will work for most people. If not, feel free to contact me or
> make changes yourself :)
>
> What is not yet done is what Karl-Heinz suggested. I think that is more a
> PicoLisp code thing that generates HTML. @Karl-Heinz: could you look into
> that?
>
> I'll try to update other pages to better match the changed possibilities as
> well.
>
> BTW I'll try and use the mailing list only for this kind of announcements to
> avoid clutter. Since I am a dinosaur I was not aware that much :)
>
> Best,
>Arie
Jean-Christophe Helary
---
http://mac4translators.blogspot.com @brandelune
