Unused since commit b8c41362f2a5c8fcc6b1846a79c72bfa77565297
("nntp: simplify the long_response API")
---
lib/PublicInbox/NNTP.pm | 1 -
1 file changed, 1 deletion(-)
diff --git a/lib/PublicInbox/NNTP.pm b/lib/PublicInbox/NNTP.pm
index 63d5870..13591e5 100644
--- a/lib/PublicInbox/NNTP.pm
+++ b/l
This can help admins diagnose problems with SolverGit, since
qspawn logs the failed "git apply" command-line in stderr.
(or it can waste admins' time because sometimes there's crap
mail clients which mangle patches)
---
lib/PublicInbox/SolverGit.pm | 2 +-
1 file changed, 1 insertion(+), 1 deleti
On Tue, 5 Feb 2019 at 16:32, Eric Wong wrote:
> The git-users mailing list is on Google Groups with obfuscated
> addresses and censored archives. We should allow users to
> import them soon, as obfuscated/censored archives are better
> than not having archives at all when Google decides to shut d
The git-users mailing list is on Google Groups with obfuscated
addresses and censored archives. We should allow users to
import them soon, as obfuscated/censored archives are better
than not having archives at all when Google decides to shut down
yet-another-service.
There's also some mangling th
We want to be able to take advantage of this in other modules
---
lib/PublicInbox/HlMod.pm | 2 ++
lib/PublicInbox/ViewVCS.pm | 3 +--
2 files changed, 3 insertions(+), 2 deletions(-)
diff --git a/lib/PublicInbox/HlMod.pm b/lib/PublicInbox/HlMod.pm
index 13f27d1..014d82f 100644
--- a/lib/Public
For user documentation regarding CSS; showing users the sample
CSS with comments is probably more helpful than having
standalone documentation on CSS classes.
---
contrib/css/216dark.css| 30 +-
lib/PublicInbox/UserContent.pm | 16 +---
lib/PublicInb
It turns out there's no point in having multiple instances of
this or having to worry about destruction or destruction
ordering.
This will make it easier to reuse the one instance we have
across different modules.
---
lib/PublicInbox/HlMod.pm | 33 +
lib/PublicIn
We'll want to use to support highlighting syntax used by
Markdown and possibly other markup languages (while retaining
the raw plain-text layout and formatting).
---
lib/PublicInbox/HlMod.pm | 15 ++-
t/hl_mod.t | 2 ++
2 files changed, 12 insertions(+), 5 deletions(-)
This is compatible with Markdown; but we still keep the WYSIWYG
nature of plain-text with this. This is only intended for use
with our documentation. Enabling any type of Markdown support
for emails can lead to incompatibilities or interopability
problems with alternative implementations.
---
li
Favor in-place utf8::decode since it's a bit faster without
method dispatch overhead; and don't care about validity just
yet.
HlMod->do_hl itself should return "utf8" strings, since other
parts of our code can use it, so it's not the job of ViewVCS to
post-process HlMod output.
---
lib/PublicInbo
Experimenting with using Markdown-style "```$LANG" blocks
support for our user documentation. It makes the CSS
example easier-to-follow when the CSS source is in front
of the user.
Markdown-style blocks definitely won't be enabled by default for
emails. I don't want to encourage people to use Ma
11 matches
Mail list logo