Pike-devel

pike-devel@lists.lysator.liu.se

1 participants
3041 discussions

Re: RFC: Attributes in Markdown text
by Chris Angelico 22 May '20

22 May '20

On Fri, May 22, 2020 at 9:28 AM Martin Nilsson (Coppermist) @ Pike (-) developers forum <10353(a)lyskom.lysator.liu.se> wrote: > > > > >How does that sound? > > > > Sounds good to me. The expectations should be to move it from Tools to > Parser (or something) also once the changes are done. Cool. The changes are done, including that move - which actually is a move *back*. For compatibility reasons, I've kept a little shim in Tools, so you can still call Tools.Markdown.parse() as before. At the moment, it's on branch rosuav/markdown-parser-extensibility but I'm fairly sure there won't be any backward compatibility problems. If anyone else can test any of their Markdown code, I'd appreciate it, just as a quick check. If no objections and no issues found, I'll merge it into master some time next week. ChrisA

1 0

Re: RFC: Attributes in Markdown text
by Chris Angelico 21 May '20

21 May '20

On Fri, May 22, 2020 at 4:00 AM Martin Nilsson (Coppermist) @ Pike (-) developers forum <10353(a)lyskom.lysator.liu.se> wrote: > > While I'm indifferent to markdown itself, my problem with the markdown > implementation in Pike is that it was implemented as an application > with no programmatic way of controlling its behavior. That's why we > moved it into the Tools module. A proper markdown module should be > easy to extened and control from code. Okay. Here's a proposal then. I'll go through the Markdown module and give it a bunch of hooks intended for subclasses, and also unprotect Parser and Lexer. Then anyone can do something like: class Renderer { inherit Tools.Markdown.Renderer; string table(string header, string body, mapping attrs) { return ::table(header, body, attrs | (["border": "1"])); } } as an easy way to make a small tweak to the behaviour. And yes, part of this would be that every HTML tag emitter would take an attrs mapping, which would then mean that my original proposal (having a specially-formatted block at the end of a paragraph) would become a simple job of subclassing the parser. (Oh, and I'd add a Parser entry to the options mapping, to make it easier and more logical to override. Same as Renderer currently is.) How does that sound? ChrisA

2 1

RFC: Attributes in Markdown text
by Chris Angelico 21 May '20

21 May '20

See branch: rosuav/markdown-attribute-syntax There's a not-very-well-known syntax supported by some Markdown parsers (including GitHub Flavored Markdown) that allows HTML attributes to be attached to a paragraph of text: Text goes here blah blah blah {: someattr=value otherattr=otherval} This is extremely handy for making small adjustments to the display of something, particularly with shorthands for class and ID, for use in CSS: {: .someclass} {: #someid} However, it's not well documented and I can't find a standard anywhere for it. It is something that I personally would find extremely useful, and am currently implementing by subclassing the Markdown module and tweaking the parser. Would anyone else find this of value? Conversely, would anyone find that this causes issues? ChrisA

3 4

Build failure on macOS (HEAD of master)
by Marc Simpson 01 May '20

01 May '20

Hi all, FYI, it looks like master no longer builds on macOS due to the MTU additions in [44f12ac]: .../src/modules/_Stdio/file.c:5526:16: error: use of undeclared identifier 'IP_MTU' int option = IP_MTU; .../src/modules/_Stdio/file.c:5541:14: error: use of undeclared identifier 'IPV6_MTU' option = IPV6_MTU; Best, Marc

1 1

SQLite query segfaults
by Marc Simpson 30 Apr '20

30 Apr '20

Hi folks, It seems that I can reliably segfault recent Pike 8.1 installs when using sprintf-style SQLite queries: $ echo ' create table demo(a, b); insert into demo(a, b) values(1, "abc")' | sqlite3 demo.db $ pike Pike v8.1 release 13 running Hilfe v3.5 [...] > Sql.Sql db = Sql.Sql("sqlite://demo.db"); > db->query("select * from demo"); (1) Result: ({ /* 1 element */ ([ /* 2 elements */ "a": "1", "b": "abc" ]) }) > db->query("select * from demo where a = :a", ([":a": 1 ])); (2) Result: ({ /* 1 element */ ([ /* 2 elements */ "a": "1", "b": "abc" ]) }) > db->query("select * from demo where a = %d", 1); Segmentation fault This occurs on both macOS and Linux; on macOS, segfaults are observed when the SQLite module is linked against either MacPorts' SQLite 3 or the system wide dylib in /usr/lib. Note that query() with a mapping argument doesn't segfault; furthermore, no such segfault occurs under Pike v8.0 release 702. Please let me know whether this is reproducible (and/or whether more information is required). Thanks, Marc

3 4

Interest in zip archive resolver?
by H William Welliver 29 Apr '20

29 Apr '20

Hello all, I’ve been going through some of my long ignored feature branches and found a few that might have promising code. Is there any interest in being able to specify (include/program/module) paths in terms of zip archives? At one point I wanted to be able to provide an entire application as a single file, and wrote support for various paths inside of zip files. The code I wrote is about 7 years old, but it was/is used and I’d be happy to fix it up if no one has major objections. The code in question provides support for including zip files as part of paths for -I, -P and -M: pike -M /path/to/some.zip or pike -M /path/to/some.zip/folder As well as the idea of a properly formatted archive with well know directories for modules, includes and programs: pike -A /path/to/some.zip where some.zip looks like: include/* modules/* And implicitly sets -I, -M and -P to include/, modules and / respectively. Any thoughts, opinions, suggestions? Bill

3 2

Re: Interest in zip archive resolver?
by Marcus Comstedt (ACROSS) (Hail Ilpalazzo!) ＠ Pike (-) developers forum 17 Apr '20

17 Apr '20

>I hadn.FN"t really thought of making it executable$B!D(B I think thereN"s a >magic cookie at the beginning of a ZIP file so a hashbang might not >work if the archive were intended to be spec-compliant. No, the magic cookie (PK\005\006) is at the _end_. The central directory and file entries also have magic cookies (PK\001\002 and PK\003\004 respectively), but those don't have to be at any specific position but are pointed out as file offsets rooted in the PK\005\006 header at offset file_size-22. AFAICR it was standard practice to make self-extracting ZIP:s on MS-DOS by just cramming an MZ binary before the archive (and adjusting the offsets accordingly). It should be pretty easy to just put something at the start if creating the archive by hand like Filesystem.Zip is doing.

1 0

Pike-bot
by Henrik Grubbstr�m (Lysator) ＠ Pike (-) developers forum 22 Mar '20

22 Mar '20

Hi The githelper instance on pike-git.lysator.liu.se has been extended to know about the gitlab issue tracker at git.lysator.liu.se. It can set and remove some labels on issues, and also close issues. The policies are relatively straight forward: * The Stalled label is always cleared. * The Doing label is set if the issue isn't resolved by this commit. * An issue is considered resolved if the commit says that it is a fix and it is committed to the appropriate branch for the milestone of the issue, in which case: * The Doing label is removed. * The To Do: Change Log label is removed if CHANGES is altered. * The Resolved::Fixed label is set if no Resolved::* label is already set. * The issue is closed if there are no remaining To Do:* labels. Updating your githelper will cause it to (by default) validate issue references in commit-messages. Enjoy! /grubba

1 0

SSL3.Context->find_cert_domain()
by william＠welliver.org 19 Mar '20

19 Mar '20

I'm looking into adding ACME ALPN challenge support to an application that uses the SSL module and I think it's possible to do that by using a custom SSL Context object; however it seems that I'd need access to the SSL Session from find_cert_domain in order to determine if the connection was requesting challenge authentication. I'm also assuming that the module doesn't otherwise cache the certificates returned from this call. Would it be unreasonable to either change the signature of find_cert_domain() to include this, or possibly add an optional method to that would get used if present (for backward compatibility reasons)? Of course, if I get it working in a reasonable fashion, I'd be happy to contribute this hypothetical ACME Context. Any thoughts? Bill

1 0

Stdio.Buffer() bug ?
by Arne Goedeke 12 Mar '20

12 Mar '20

Commit 20d1fa961d0059657d471d700ce63bcb3ab9d3ca mentions that there is a bug in the Stdio.Buffer support in Stdio.File()->write() (I assume). Stephen, can you explain how it is broken? Do you have a test case? Does it have something to do with the fact that you are using a subclass of Stdio.Buffer? Arne

4 8

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

Pike-devel