Re: [basex-talk] reply to 2. docker basexhttp wrong owner of /srv/basex/* (scbh)
Hi Rob, thanks for the tip that's what i already do, but far from ideal is it normal ? a bug ? related to my env ? i can't figure it out bach On mardi 7 décembre 2021 12:37:00 CET Rob Stapper wrote: > Hi Bach, > > Login as super-user[1] in your running container to change ownerschip. > > [1] docker exec -u 0 -it bash > > Succes, > Rob > > Sent from Mail for Windows > > > >
[basex-talk] reply to 2. docker basexhttp wrong owner of /srv/basex/* (scbh)
Hi Bach, Login as super-user[1] in your running container to change ownerschip. [1] docker exec -u 0 -it bash Succes, Rob Sent from Mail for Windows -- This email has been checked for viruses by Avast antivirus software. https://www.avast.com/antivirus
Re: [basex-talk] Didn't know ....
I'll wait for the Winter Edition since I easily could re-arrange for the specific point. But your usual effort is well appreciated! Thanks Chrisitan. M. On 07/12/21 11:40, Christian Grün wrote: …fixed and deployed [1]. BaseX 9.6.4 will be released in December. [1] https://files.basex.org/releases/latest/ On Tue, Dec 7, 2021 at 11:04 AM Christian Grün wrote: …definitely a (fairly new) bug, and one that should be fixed soon [1]. I have opened an issue to track this down. Thanks, Christian [1] https://github.com/BaseXdb/basex/issues/2054 On Tue, Dec 7, 2021 at 10:31 AM Martin Honnen wrote: Am 07.12.2021 um 10:16 schrieb Marco Lettere: Hi all, Just because "abc" || () returns "abc", it felt natural to me that should return but I get instead. This is on a 9.6.1. I can't recall whether this has always been like that thus it's one of my xquery shortcomings or if actually something strange is going on here ... I would see that as a BaseX bug.
Re: [basex-talk] Didn't know ....
…fixed and deployed [1]. BaseX 9.6.4 will be released in December.
[1] https://files.basex.org/releases/latest/
On Tue, Dec 7, 2021 at 11:04 AM Christian Grün
wrote:
>
> …definitely a (fairly new) bug, and one that should be fixed soon [1].
> I have opened an issue to track this down.
>
> Thanks,
> Christian
>
> [1] https://github.com/BaseXdb/basex/issues/2054
>
>
> On Tue, Dec 7, 2021 at 10:31 AM Martin Honnen wrote:
> >
> >
> > Am 07.12.2021 um 10:16 schrieb Marco Lettere:
> > > Hi all,
> > >
> > > Just because "abc" || () returns "abc", it felt natural to me that > > attr="abc{()}"/> should return but I get
> > > instead.
> > >
> > > This is on a 9.6.1.
> > >
> > > I can't recall whether this has always been like that thus it's one of
> > > my xquery shortcomings or if actually something strange is going on
> > > here ...
> > >
> > >
> >
> > I would see that as a BaseX bug.
> >
Re: [basex-talk] Didn't know ....
…definitely a (fairly new) bug, and one that should be fixed soon [1].
I have opened an issue to track this down.
Thanks,
Christian
[1] https://github.com/BaseXdb/basex/issues/2054
On Tue, Dec 7, 2021 at 10:31 AM Martin Honnen wrote:
>
>
> Am 07.12.2021 um 10:16 schrieb Marco Lettere:
> > Hi all,
> >
> > Just because "abc" || () returns "abc", it felt natural to me that > attr="abc{()}"/> should return but I get
> > instead.
> >
> > This is on a 9.6.1.
> >
> > I can't recall whether this has always been like that thus it's one of
> > my xquery shortcomings or if actually something strange is going on
> > here ...
> >
> >
>
> I would see that as a BaseX bug.
>
Re: [basex-talk] Output script-element with javascript source code
Thank you Martin! I used output method "xhtml". After changing it to "html" the
string was not escaped any longer. Great!
Best regards,
Kristian Kankainen
> On 7. Dec 2021, at 11:27, Martin Honnen wrote:
>
>
> Am 07.12.2021 um 10:00 schrieb Kristian Kankainen:
>> Hi all,
>>
>> Can I somehow control the serialization of element contents? I want to use
>> Xquery to generate parts of source code for javascript and put the generated
>> code inside a script element on the webpage. Basically this:
>>
>> define function web:display-graph($term) {
>>
>> {
>> string-join((
>> 'd3.select("#graph").graphviz().renderDot(',
>> "'digraph {a -> b}'",
>> ');'
>> ), out:nl())
>> }
>>
>> }
>>
>> But it doesn't work as the > character gets replaced with its corresponding
>> HTML entity >. Is there a way to circumvent this behaviour?
>>
>
> At which point or how/where do you serialize that "script" element? With
> output method "html" the escaping should not take place.
Re: [basex-talk] Didn't know ....
Am 07.12.2021 um 10:16 schrieb Marco Lettere: Hi all, Just because "abc" || () returns "abc", it felt natural to me that should return but I get instead. This is on a 9.6.1. I can't recall whether this has always been like that thus it's one of my xquery shortcomings or if actually something strange is going on here ... I would see that as a BaseX bug.
Re: [basex-talk] Output script-element with javascript source code
Am 07.12.2021 um 10:00 schrieb Kristian Kankainen:
Hi all,
Can I somehow control the serialization of element contents? I want to use
Xquery to generate parts of source code for javascript and put the generated
code inside a script element on the webpage. Basically this:
define function web:display-graph($term) {
{
string-join((
'd3.select("#graph").graphviz().renderDot(',
"'digraph {a -> b}'",
');'
), out:nl())
}
}
But it doesn't work as the > character gets replaced with its corresponding HTML
entity >. Is there a way to circumvent this behaviour?
At which point or how/where do you serialize that "script" element? With
output method "html" the escaping should not take place.
[basex-talk] Didn't know ....
Hi all,
Just because "abc" || () returns "abc", it felt natural to me that attr="abc{()}"/> should return but I get
instead.
This is on a 9.6.1.
I can't recall whether this has always been like that thus it's one of
my xquery shortcomings or if actually something strange is going on here ...
Thanks for clarifications.
Marco.
[basex-talk] Output script-element with javascript source code
Hi all,
Can I somehow control the serialization of element contents? I want to use
Xquery to generate parts of source code for javascript and put the generated
code inside a script element on the webpage. Basically this:
define function web:display-graph($term) {
{
string-join((
'd3.select("#graph").graphviz().renderDot(',
"'digraph {a -> b}'",
');'
), out:nl())
}
}
But it doesn't work as the > character gets replaced with its corresponding
HTML entity >. Is there a way to circumvent this behaviour?
Best regards
Kristian Kankainen
