Re: documentation location

> On Jan 5, 2019, at 2:20, Alexander Burger wrote: > > Hi Jean-Christophe, > >> Here is diff for the whole setting. > > Cool, many thanks for this great improvement! > > > I have installed it. And the table in https://picolisp.com/wiki/?help looks > very > nice indeed :) The point being

Re: documentation location

Hi Jean-Christophe, > Here is diff for the whole setting. Cool, many thanks for this great improvement! I have installed it. And the table in https://picolisp.com/wiki/?help looks very nice indeed :) ☺/ A!ex -- UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe

Re: documentation location

Alex,Thank you for your patience. And thank you for the explanations.What I did was check the code that was the closest to what I wanted, it was the code for the tag, and tried to understand how it was working, and, well, I did not understand everything :)Ok, I have something that works. Here is a

Re: documentation location

Hi Jean-Christophe, I'm not good in CSS, so lets assume your proposal is correct, then > ("%" # Table >(let Nm (till "}" T) > (prin "") > (ht:Prin Nm) > (prin "" ) ) ) this will not work, as (let Nm (till "}" T) ... terminates on the *next* "}", but the table elements are

Re: documentation location

Alex, The conclusion of my investigation is 1) tables created in wiki syntax must be different from the tables that are not user created → adding a class="wiki" to their html should be enough 2) to make sure that the CSS applies only to such tables the CSS should be modified this way:

Re: documentation location

> On Jan 4, 2019, at 9:35, Jean-Christophe Helary wrote: > > It looks like there is a glitch in the table CSS rendering. And I'm not sure > it is a browser cache issue... I'm investigating and if I find a solution > I'll get back to you. That was a browser cache issue :) But the unexpected

Re: documentation location

>> /* Table styles */ >> table,td { >>border-collapse: collapse; >>border: 1px midnightblue solid; >>padding: 3px; >> } > > Cool, that's easy! :) > > Released and installed. Nice ! :) I just added a table to illustrate the table markup. It looks like there is a glitch in the table

Re: documentation location

On Thu, Jan 03, 2019 at 09:38:04PM +0900, Jean-Christophe Helary wrote: > Here is the diff for a very simple css for the table. > Basically just this: > > /* Table styles */ > table,td { > border-collapse: collapse; > border: 1px midnightblue solid; > padding: 3px; > } Cool, that's ea

Re: documentation location

Alex, The help page is updated. I guess the emacs mode should be too but I can't do that today. Jean-Christophe > On Jan 3, 2019, at 19:11, Alexander Burger wrote: > > Hi Jean-Christophe, > > On Sun, Dec 30, 2018 at 05:09:45PM +0100, Alexander Burger wrote: >> Another option could be '%' to

Re: documentation location

Alex,Here is the diff for a very simple css for the table.Basically just this:/* Table styles */table,td {    border-collapse: collapse;    border: 1px midnightblue solid;    padding: 3px;}JC wiki.css.diff Description: Binary data On Jan 3, 2019, at 19:11, Alexander Burger w

Re: documentation location

Alex, It works fine. There is just a need for some CSS to make it look better. I'll propose something later. I'll update the documentation shortly. Jean-Christophe > On Jan 3, 2019, at 19:11, Alexander Burger wrote: > > Hi Jean-Christophe, > > On Sun, Dec 30, 2018 at 05:09:45PM +0100, Alexa

Re: documentation location

Hi Jean-Christophe, On Sun, Dec 30, 2018 at 05:09:45PM +0100, Alexander Burger wrote: > Another option could be '%' to open the table. The other two '~' and '|' are > also still free. So I put an absolutely minimal table syntax into "wiki/lib.l". Better than no table at all ;) I've installed it

Re: documentation location

On Mon, Dec 31, 2018 at 12:49:33AM +0900, Jean-Christophe Helary wrote: > >> [{ ~{ |{...} |{...}} > ... > > Not a very good idea. It introduces '[' as a new meta-character. Then you > > have > I'm not sure I understand here. If [ comes before { why would it become a new > meta-character? > Sorry

Re: documentation location

> On Dec 31, 2018, at 0:26, Alexander Burger wrote: >> It could be: >> >> [{ ~{ |{...} |{...}} >> ~{ |{...} |{...}}} > > Not a very good idea. It introduces '[' as a new meta-character. Then you have > to escape it whenever '[' appears in the normal text, and have to document it > as > a

Re: documentation location

On Sun, Dec 30, 2018 at 11:40:55PM +0900, Jean-Christophe Helary wrote: > t{ r{ c{...} c{...}} >r{ c{...} c{...}}} > Of course, it doesn't have to be t, r, c. This would work. > It could be: > > [{ ~{ |{...} |{...}} >~{ |{...} |{...}}} Not a very good idea. It introduces '[' as a new m

Re: documentation location

> On Dec 30, 2018, at 23:11, Alexander Burger wrote: > > Hi Jean-Christophe, > >> I wanted to use tables for that but could not find them in the wiki syntax... >> Checking the lib.l in the wiki code I found that it seemed relatively simple >> to add them. > >> Is it a design choice to not ha

Re: documentation location

Hi Jean-Christophe, > I wanted to use tables for that but could not find them in the wiki syntax... > Checking the lib.l in the wiki code I found that it seemed relatively simple > to add them. > Is it a design choice to not have included them ? I never really thought about adding tables. Is it

Re: documentation location

Alex, >> On a side note, I just modified the layout of the following page: >> https://picolisp.com/wiki/?AtMark >> >> instead of using preformated markup I used a more linear flow with a list, >> and >> I put more specific links to the references when it was possible. > > Looks good :) I wante

Re: documentation location

Hi Jean-Christophe, > It looks like on debian the documentation is put in > /usr/share/doc/picolisp/ > > is it the standard location on linux ? In fact the documentation is looked up at "@doc/", i.e. relative to the installation directory. So if picolisp is in "/usr/lib/picolisp" (as it is on D

documentation location

It looks like on debian the documentation is put in /usr/share/doc/picolisp/ is it the standard location on linux ? I'm asking because the picolisp mode hosted on melpa looks for the doc at: /usr/share/picolisp/doc/ and obviously doesn't find it... On a side note, I just modified the layout of