Search results for "plugin" - Dillo-dev

Re: XMPP PubSub Plugin

by Schimon Jehudah

Good evening! I have made an XMPP plugin for Dillo. I would be grateful for your feedbacks. I would also need instructions as to how to implement configurations. Compulsory options: * JabberID * Password Possible options: * Connection * Timeout I consider to add an interface for JabberID and Password, and I would rather receive instructions from the staff. It is posible to use anonymous accounts, such as anon(a)anon.jabberfr.org, yet I would rather not do so, because: * Most of the anonymous accounts have PubSub disabled, which is exactly the needed feature which this plugin provides. * I do not want to rely on anonymous accounts or any server, because of changes that might occur in any future. P.S. I did not think, that I would be sending a plugin as early as now. Kind regards, Schimon On Thu, 7 Nov 2024 07:45:33 +0200 Schimon Jehudah <sch(a)fedora.email> wrote: > Good day, to one and all! > > My name is Schimon, I am a pianist, attorney at law, and I also work > on software that mainly involve the technologies of Syndication and > XMPP. > > My current intention, is to design an XMPP client, based on Slixmpp, > to allow Dillo to interact with Atom Over XMPP (XEP-0277 and > XEP-0472). > > Atom Over XMPP specifies storage of textual content (be it text or > HTML) on XMPP PubSub nodes. It is useful for publishing (see Libervia, > Movim, Rivista XJP), annotating resources (see Blasta) and for any > sort of mean which may require textual content. > > References: > https://blasta.woodpeckersnest.eu/help/about/xmpp/atomsub > https://blasta.woodpeckersnest.eu/help/about/xmpp/pubsub > > Projects: > https://schapps.woodpeckersnest.eu/blasta/ > https://schapps.woodpeckersnest.eu/rivista/ > > I intend to utilize the Python computer language for this task. > > Any help, encouragement, and especially accompanying (not in the > musical sense) my efforts be welcome. > > This is my first time which I intend to collaborate with Dillo > developers, and I am excited by this opportunity. > > Kind regards, > Schimon

Nov. 9, 2024

Re: Firefox bookmarks plugin

by a1ex＠dismail.de

Hi, On Fri, 30 Aug 2024 10:58:57 +0200 Diego <darkspirit5000(a)gmail.com> wrote: > > It doesn't require describing the available dpis in the file. Not > > sure what would be the advantage of doing so. > > For reference. To explain to the user how to switch between a built-in > DPI and another DPI for the same service. I think this part in the docs[0] covers it: "Plugins are searched in the ~/.dillo/dpi/ directory first, and then in the system directory if not found. The dpi_dir option sets the system dpi directory and must be specified once." [0] https://dillo-browser.github.io/user_help.html#dpidrc It seems reasonable to me, but if you have a better way of wording it, that might be the best place to start. Regards, Alex

Aug. 30, 2024

https plugin status

by onepoint＠starurchin.org

On Fri, Mar 14, 2008 at 07:19:45PM +0100, Christian Kellermann wrote: > Dear list, > > is the https plugin supposed to work? My take on the status of https is that it's currently my biggest itch! :-) I've been gdb-ing dillo-fltk (looking at it from the other end from you, as it were), and I can see the CCC setting up tearing down the IO links, so it looks as though the dillo process is talking to something, and getting something sensible from it. But AFAICT the https filter dpi isn't even starting (it should dump some startup messages to stdout which I'm not seeing). Like you I'd appreciate some guidance from those wiser than myself. Getting https working would greatly reduce the number of times I run Firefox! Regards, Jeremy Henty

March 15, 2008

claws? (Re: [Dillo-dev] Garbage chars added)

by jcid＠dillo.org

On Thu, Oct 23, 2008 at 08:27:13PM +0300, Henri Salo wrote: > On Thu, 23 Oct 2008 16:31:14 +0000 > "corvid" <corvid(a)lavabit.com> wrote: > > > Tomas wrote: > > > X-Mailer: Claws Mail 3.5.0 (GTK+ 2.12.0; i486-pc-linux-gnu) > > > > Just noticed this. Is claws able to make much use of dillo2? > > Jorge put in a special-case workaround for "dillo -l -f -x XID URL" > > right before release, but I don't know whether anyone's using it > > (or if any claws users even know it's there) > > > > Hmm...a moment of searching and the first hit I get is > > http://www.nabble.com/Using-of-Dillo2-td20014194.html > > which suggests that, no, they don't know. > > They know. Both users and development. I said about Dillo2 in #claws > when it was release. I'm not sure when they are going to implement it > as plugin nor if it already works. Some information can be located in > two places: > > http://www.claws-mail.org/plugin.php?plugin=dillo > http://www.claws-mail.org/plugins.php?branch=STD The problem is dillo-2.0 has a workaround only implementation for the CLI switches claws needs. It'd be good to patch it fully, but before that we need to know whether is possible to embed an FLTK2 window into an Xwindow. Once we know it's possible, the patch is in place and the release made, I'd advice claws folks to use it. -- Cheers Jorge.-

Oct. 23, 2008

SSL in the browser

by andreas＠kemnade.info

Hi, On Tue, 21 Oct 2014 11:29:06 -0300 Jorge Arellano Cid <jcid at dillo.org> wrote: > Hi corvid, > > On Mon, Oct 20, 2014 at 11:47:35PM +0000, eocene wrote: > > I wrote: > > > http://www.dillo.org/test/ssl_in_browser.diff > > > > Fixed a couple of bugs, added a couple of features, new version up. > > Oh, as our mailsearch doesn't work anymore, is there > and URL to the original thread (Gmane style) or something? > > I'd like to remember what the main point of having SSL inside > the browser were. I'm getting old. ;) > here is a list of subjects which contain https, maybe that helps a bit. 2003-June.txt:Subject: [Dillo-dev] HTTPS support 2003-March.txt:Subject: [Dillo-dev] https approaches? 2003-March.txt:Subject: [Dillo-dev] Re: https approaches? 2003-November.txt:Subject: [Dillo-dev] Re: https dpi 2003-November.txt:Subject: [Dillo-dev] HTTPS Patch 2003-November.txt:Subject: [Dillo-dev] tabs, https, ... 2003-November.txt:Subject: [Dillo-dev] Small bug with combined frames/tabs/https patch and gcc 2.9x 2003-November.txt:Subject: [Dillo-dev] Small bug with combined frames/tabs/https patch 2003-November.txt:Subject: [Dillo-dev] [PATCH] HTTPS version 2. 2003-October.txt:Subject: [Dillo-dev] HTTPS patch 2003-October.txt:Subject: [Dillo-dev] HTTPS Patch 2004-February.txt:Subject: [Dillo-dev] Re: https dpi 2004-January.txt:Subject: [Dillo-dev] Re: https dpi 2004-July.txt:Subject: [Dillo-dev]https 2004-July.txt:Subject: [Dillo-dev]HTTPS 2004-July.txt:Subject: [Dillo-dev]Re: HTTPS 2004-July.txt:Subject: [Dillo-dev]dpip dialog for https (and dpis in general) 2004-July.txt:Subject: [Dillo-dev]https patch 2004-July.txt:Subject: [Dillo-dev]dpip dialog for https (and dpis in general) 2004-July.txt:Subject: [Dillo-dev]More https goodness 2004-July.txt:Subject: [Dillo-dev]Replying to lists (was: dpip dialog for https (and dpis in general)) 2004-July.txt:Subject: [Dillo-dev]More https goodness 2004-July.txt:Subject: [Dillo-dev]HTTPS certificate support 2004-July.txt:Subject: [Dillo-dev]HTTPS Cleanup 2004-June.txt:Subject: [Dillo-dev]https (eg for posting to ps2 bulletin boards) 2004-March.txt:Subject: [Dillo-dev]Re: https hungs dillo up... 2004-May.txt:Subject: [Dillo-dev]https (eg for posting to ps2 bulletin boards) 2004-November.txt:Subject: [Dillo-dev]https by lynx -source 2004-September.txt:Subject: [Dillo-dev]https 2005-February.txt:Subject: [Dillo-dev]testing https plugin gave problems 2005-January.txt:Subject: [Dillo-dev]https, ssl & certificates 2005-July.txt:Subject: [Dillo-dev]cookies dpi over https and dpi framework 2005-June.txt:Subject: [Dillo-dev]cookies dpi over https and dpi framework 2007-October.txt:Subject: [Dillo-dev] https and OpenBSD 2008-April.txt:Subject: [Dillo-dev] [PATCH]: Fixing https step 1: Have a basic dpi dialog 2008-April.txt:Subject: [Dillo-dev] [PATCH]: Fixing https step 1: Have a basic dpi 2008-April.txt:Subject: [Dillo-dev] [PATCH]: Fixing https step 1: Have a basic dpi dialog 2008-April.txt:Subject: [Dillo-dev] [PATCH]: Fixing https step 1: Have a basic dpi 2008-March.txt:Subject: [Dillo-dev] https plugin status 2008-March.txt:Subject: [Dillo-dev] [PATCH]: send the https dpi plugin debug messages to the 2008-March.txt:Subject: [Dillo-dev] https plugin status 2008-March.txt:Subject: [Dillo-dev] [PATCH]: Fixing https step 1: Have a basic dpi dialog 2008-March.txt:Subject: [Dillo-dev] [PATCH]: Fixing https step 1: Have a basic dpi 2008-March.txt:Subject: [Dillo-dev] [PATCH]: Fixing https step 1: Have a basic dpi dialog 2008-March.txt:Subject: [Dillo-dev] https plugin status 2008-March.txt:Subject: [Dillo-dev] [PATCH]: Fixing https step 1: Have a basic dpi 2008-March.txt:Subject: [Dillo-dev] https plugin status 2008-March.txt:Subject: [Dillo-dev] [PATCH]: Fixing https step 1: Have a basic dpi dialog 2008-March.txt:Subject: [Dillo-dev] https plugin status 2008-November.txt:Subject: [PATCH] Update the GPL version in the OpenSSL exception clause in dpi/https.c 2008-November.txt:Subject: [Dillo-dev] A warning about HTTPS and proxies 2008-October.txt:Subject: [PATCH] https: Improve the plugin warnings when SSL is disabled. 2008-October.txt:Subject: [Dillo-dev] https error handling 2008-October.txt:Subject: [PATCH] Update the GPL version in the OpenSSL exception clause in dpi/https.c 2009-July.txt:Subject: [Dillo-dev] [patch] check for dpip_tag == NULL in https.c 2009-June.txt:Subject: patch: Re: [Dillo-dev] https through a proxy 2009-May.txt:Subject: [Dillo-dev] https through a proxy 2009-May.txt:Subject: patch: Re: [Dillo-dev] https through a proxy 2010-January.txt:Subject: [Dillo-dev] experimental patch: gnutls for the https dpi 2010-October.txt:Subject: [Dillo-dev] Https remote certificate cannot be verified 2011-December.txt:Subject: [Dillo-dev] IPv6 and HTTPS (Re: release candidate for dillo-3.0.2) 2011-December.txt:Subject: [Dillo-dev] IPv6 and HTTPS (Re: release candidate for 2012-October.txt:Subject: [Dillo-dev] https unpleasantness 2013-February.txt:Subject: [Dillo-dev] https related crash 2013-March.txt:Subject: [Dillo-dev] https related crash Greetings Andreas Kemnade

Oct. 21, 2014

Re: Firefox bookmarks plugin

by Rodrigo Arias

Hi, On Mon, Aug 26, 2024 at 01:31:13AM +0200, Diego wrote: >Good work and very interesting idea. Thanks! >If I can suggest a change I would add this lines to dpidrc at Makefile >the installation > ># Default dillo bookmarks dpi >#bookmarks=bookmarks/bookmarks.dpi ># ffbm: A Dillo plugin to sync bookmarks with Firefox >bookmarks=$(DPI_DIR)/$(BIN) > > >maybe it's time to patch dpidrc to make it more descriptive > >I sugest this >dpi_dir=/usr/local/lib/dillo/dpi > ># standard dillo distributed DPIs >#bookmarks=bookmarks/bookmarks.dpi >#cookies=cookies/cookies.dpi >#downloads=downloads/downloads.dpi >#vsource=vsource/vsource.filter.dpi The file dpidrc only registers the protocols (ftp: -> ftp dpi), the dpis are taken from the dpi_dir or ~/.dillo/dpi automatically. It doesn't require describing the available dpis in the file. Not sure what would be the advantage of doing so. Best, Rodrigo.

Aug. 27, 2024

Connection problems on Mac OS X 10.6.7

by obeythepenguin＠gmail.com

On Fri, 27 May 2011 13:38:43 -0400, reza farivar <rf.opensource(a)gmail.com> wrote: > Yes. Well, the only plugin I could see is the save button on the panel, > and > it can successfully navigate the filesystem and save a page correctly. That one isn't a plugin, actually. Does the bookmarks button work? (Dillo's plugins right now are bookmarks, cookies, downloads, view source, and data/file/ftp/https URIs. They're not Flash-type graphical plugins, but things that really should be built into the browser.) > Yes, Here's the result. I tried it a couple of times, and this looks like > the culprit: > > #13 0x000000010007d373 in do_queued_events () at style.hh:554 > #14 0x000000010007ffa0 in fl_mac_flush_and_wait () at style.hh:554 > #15 0x0000000100083c6f in Fl::run () at style.hh:554 > > Those three lines are consistent everytime I break in GDB. The more > detailed > ones are different of course. Here's one, just in case: > > #0 0x00007fff87967dc5 in tiny_malloc_from_free_list () > #1 0x00007fff87966fdd in szone_malloc_should_clear () > #2 0x00007fff8799d32b in szone_memalign () > #3 0x00007fff879a46eb in malloc_zone_memalign () > #4 0x00007fff87376608 in CFSortIndexes () > #5 0x00007fff87376480 in CFQSortArray () > #6 0x00007fff87386ad2 in __CFRunLoopDoObservers () > #7 0x00007fff87361da4 in CFRunLoopRunSpecific () > #8 0x00007fff842457ee in RunCurrentEventLoopInMode () > #9 0x00007fff842455f3 in ReceiveNextEventCommon () > #10 0x00007fff842454ac in BlockUntilNextEventMatchingListInMode () > #11 0x00007fff85739e64 in _DPSNextEvent () > #12 0x00007fff857397a9 in -[NSApplication > nextEventMatchingMask:untilDate:inMode:dequeue:] () > #13 0x000000010007d373 in do_queued_events () at style.hh:554 > #14 0x000000010007ffa0 in fl_mac_flush_and_wait () at style.hh:554 > #15 0x0000000100083c6f in Fl::run () at style.hh:554 > #16 0x0000000100003a85 in main (argc=1, argv=0x7fff5fbff828) at > dillo.cc:431 It looks like the problem's somewhere in FLTK. I'll take a look and see what I can find. Cheers, ~Benjamin

May 27, 2011

claws? (Re: [Dillo-dev] Garbage chars added)

by fgeek＠hack.fi

On Thu, 23 Oct 2008 15:16:28 -0300 Jorge Arellano Cid <jcid(a)dillo.org> wrote: > On Thu, Oct 23, 2008 at 08:27:13PM +0300, Henri Salo wrote: > > On Thu, 23 Oct 2008 16:31:14 +0000 > > "corvid" <corvid(a)lavabit.com> wrote: > > > > > Tomas wrote: > > > > X-Mailer: Claws Mail 3.5.0 (GTK+ 2.12.0; i486-pc-linux-gnu) > > > > > > Just noticed this. Is claws able to make much use of dillo2? > > > Jorge put in a special-case workaround for "dillo -l -f -x XID > > > URL" right before release, but I don't know whether anyone's > > > using it (or if any claws users even know it's there) > > > > > > Hmm...a moment of searching and the first hit I get is > > > http://www.nabble.com/Using-of-Dillo2-td20014194.html > > > which suggests that, no, they don't know. > > > > They know. Both users and development. I said about Dillo2 in #claws > > when it was release. I'm not sure when they are going to implement > > it as plugin nor if it already works. Some information can be > > located in two places: > > > > http://www.claws-mail.org/plugin.php?plugin=dillo > > http://www.claws-mail.org/plugins.php?branch=STD > > The problem is dillo-2.0 has a workaround only implementation > for the CLI switches claws needs. > > It'd be good to patch it fully, but before that we need to know > whether is possible to embed an FLTK2 window into an Xwindow. > > Once we know it's possible, the patch is in place and the release > made, I'd advice claws folks to use it. You should communicate directly with Claws-Mail's development team for sure. -- Henri Salo <fgeek at hack.fi> +358407705733 GPG ID: 2EA46E4F fp: 14D0 7803 BFF6 EFA0 9998 8C4B 5DFE A106 2EA4 6E4F

Oct. 23, 2008

Re: dillo displays corrupted data using gopher protocol

by Ben Collver

Hi Rodrigo, On Tue, May 26, 2026 at 12:30:18AM +0200, Rodrigo Arias wrote: > I don't observe it here, which gopher plugin are you using and which commit? I am using commit a32f74522f990c46415977afcd06d0e8d162ea55 of the following gopher plugin: https://git.dillo-browser.org/plugins/gopher > You can likely invoke it manually with: > > $ dpidc stop > $ dpid & > $ key=$(cat ~/.dillo/dpid_comm_keys | cut -d " " -f2) > $ url="gopher://tilde.pink/1/~bencollver/log/2026-01-04-m1-macro-processor-retreat/readme.map" > $ echo "<cmd='auth' msg='$key' '><cmd='open_url' url='$url' '>\n" |\ > ~/.dillo/dpi/gopher/gopher.filter.dpi > > Perhaps using strace or gdb may help. Thanks! I built it with: CFLAGS = -std=c99 -D_POSIX_C_SOURCE=200112 -g I am including my gdb session below [1]. I tried setting a breakpoint at line 349, watching the variables, and stepping through the code with gdb's `n` command, but in that context the plugin no longer gives SIGSEGV. Any more suggestions? Thanks again, -Ben [1] gdb output: Program received signal SIGSEGV, Segmentation fault. 0x000000000040209c in read_line (buf=0x7fffffffdefb "\255\362Գ(\233G^\240Q0\335u.x86_64", len=18446744073709540501) at gopher.filter.dpi.c:331 331 for (i = 0; i < len && buf[i] != '\r' && buf[i] != '\n'; i++); (gdb) bt #0 0x000000000040209c in read_line ( buf=0x7fffffffdefb "\255\362Գ(\233G^\240Q0\335u.x86_64", len=18446744073709540501) at gopher.filter.dpi.c:331 #1 0x00000000004021e9 in read_response (s=3) at gopher.filter.dpi.c:355 #2 0x000000000040235a in render_dir (s=3, url=0x7fffffffd680 "gopher://tilde.pink/1/~bencollver/log/2026-01-04-m1-macro-processor-retreat/readme.map") at gopher.filter.dpi.c:384 #3 0x0000000000402823 in respond ( url=0x7fffffffd680 "gopher://tilde.pink/1/~bencollver/log/2026-01-04-m1-macro-processor-retreat/readme.map") at gopher.filter.dpi.c:466 #4 0x00000000004028ca in main () at gopher.filter.dpi.c:490 (gdb) up #1 0x00000000004021e9 in read_response (s=3) at gopher.filter.dpi.c:355 (gdb) p buf $3 = "i# 2026-01-04 - M1 Macro Processor Retreat\000Err\000null.host\000\061\000\000i\000Err\000null.host\000\061\000\000iI wrote a prototype gopher front-end to the Internet Archive. It was\000Err\000null.host\000\061\000\000ia single file AWK script using C"... (gdb) p start $4 = 12555

May 25, 2026

Re: dillo plugin patches

by Rodrigo Arias

Hi, I added an exception for your email to the list. Following replies should get archived. On Fri, Oct 31, 2025 at 11:34:04AM -0400, John McCue wrote: >Hi Rodrigo, > >Attached are these 3 patches, the third one is >a very minor one for the gemini plugin's Makefile. Thanks for the patches. >1. io.txt -- A patch to io.c to avoid a compile error > on OpenBSD. This is based upon the email I responded to > earlier today. > >2. dpi.txt -- Corrects an odd issue on OpenBSD with the > gopher plugin. Access a gopher hole works fine on first > try, accessing a 2nd hole does nothing, no data is > presented. Selecting the "Stop" button in dillo works to > stop the attempted load. My wild guess is one of the > casts fixed the issue. I cannot reproduce this, with or without the patch. Tested in order: - gopher://gopher.quux.org:70/1/ - gopher://gopher.floodgap.com/ If you can reliably reproduce this, you could dump the backtrace while is "doing nothing" in case it got stuck in some network operation. >3. gemini_mk.txt -- a simple change to the gemini plugin's > Makefile. It allows the gemini plugin to 'compile' on > NetBSD. NetBSD installs packages in /usr/pkg. > >As mentioned in the last email, I will be happy to test >on OpenBSD and NetBSD. > >Thanks >John >diff --git a/dpi.c b/dpi.c >index 7b38800..52547f8 100644 >--- a/dpi.c >+++ b/dpi.c >@@ -7,7 +7,7 @@ > #include "io.h" > > static void check_auth() { >- char buf[30]; >+ char buf[31]; > int rc; > char key[4], local_key[4]; > char keys[128]; >@@ -16,16 +16,16 @@ static void check_auth() { > rc = read_all(STDIN_FILENO, buf, 29); > if (rc < 0) err(1, "read auth"); > buf[30] = '\0'; >- rc = sscanf(buf, "<cmd='auth' msg='%4x' '>", key); >+ rc = sscanf(buf, "<cmd='auth' msg='%4x' '>", (unsigned int *) key); The address of key may not be aligned to the size of a word. Some architectures will cause an invalid access trying to write an int to a non-aligned address. A better solution is to declare key as an unsigned int. I applied your fixes and then changed the key variables. > if (rc < 0) err(1, "auth: %.*s", 29, buf); > if (rc < 1) errx(1, "auth: %.*s", 29, buf); > home = getenv("HOME"); > if (!home) home = "."; > sz = read_file(keys, sizeof(keys), "%s/.dillo/dpid_comm_keys", home); > if (sz < 0) err(1, "read dillo comm keys"); >- rc = sscanf(keys, "%*d %4x' '>", local_key); >- if (rc < 0) err(1, "comm key: %.*s", sz, keys); >- if (rc < 1) errx(1, "comm key: %.*s", sz, keys); >+ rc = sscanf(keys, "%*d %4x' '>", (unsigned int *) local_key); >+ if (rc < 0) err(1, "comm key: %.*s", (int) sz, keys); >+ if (rc < 1) errx(1, "comm key: %.*s", (int) sz, keys); > if (memcmp(key, local_key, 4)) errx(1, "wrong dillo key"); > } > >@@ -38,7 +38,7 @@ static void get_url(char *url_buf, size_t url_len) { > rc = read_all(STDIN_FILENO, buf, sizeof(buf)); > if (rc < 0) err(1, "read open_url"); > if (strncmp(buf, "<cmd='open_url' url='", 21)) { >- err(1, "bad open_url cmd: %.*s", sizeof(buf), buf); >+ err(1, "bad open_url cmd: %.*s", (int) sizeof(buf), buf); > } > len = url_len; > rc = read_some(STDIN_FILENO, url_buf, &len); >@@ -48,7 +48,7 @@ static void get_url(char *url_buf, size_t url_len) { > if (url_buf[i] == '\'' && url_buf[i+1] == ' ') break; > } > if (i > len-3 || strncmp(url_buf + i, "' '>", 4)) { >- err(1, "bad url end: %.*s", len, url_buf); >+ err(1, "bad url end: %.*s", (int) len, url_buf); > } > url_buf[i] = '\0'; > } >diff --git a/Makefile b/Makefile >index 1ff7047..e41e173 100644 >--- a/Makefile >+++ b/Makefile >@@ -13,6 +13,7 @@ $(DPIDRC): > mkdir -p $(DPI_DIR) > if [ -f /etc/dillo/dpidrc ]; then cp /etc/dillo/dpidrc $@; \ > elif [ -f /usr/local/etc/dillo/dpidrc ]; then cp /usr/local/etc/dillo/dpidrc $@; \ >+ elif [ -f /usr/pkg/etc/dillo/dpidrc ]; then cp /usr/pkg/etc/dillo/dpidrc $@; \ > else echo "Can't find dpidrc, is dillo installed?"; false; fi This is not in our upstream, but I would rather avoid having each possible path here. I added a DILLO_PREFIX variable, empty by default. So you can use `make install DILLO_PREFIX=/usr/pkg` to find dpidrc in your system. By default it only looks at /etc/dillo/dpidrc. > install-proto: $(DPIDRC) >diff --git a/io.c b/io.c >index 615f346..f437c2e 100644 >--- a/io.c >+++ b/io.c >@@ -7,6 +7,7 @@ > #include <fcntl.h> > #include <netdb.h> > #include <netinet/in.h> >+#include <sys/socket.h> Applied. > > #include "io.h" > I fixed several other problems and set the C standard to C99 and enabled POSIX 2001 by default in CFLAGS. I also performed the build with gcc and clang on Linux with -Werror -Wall -Wextra -pedantic as well as with -fsanitize=address to see if I catch something while running the plugin. Nothing so far. I pushed it here (we are moving away from GitHub): https://git.dillo-browser.org/plugins/gopher/log/?h=fix-bsd Let me know if you encounter problems building it on any BSD. Thanks!, Rodrigo.

Oct. 31, 2025

Dillo-dev search results for query "plugin"