From: voidlinux-github@inbox.vuxu.org
To: ml@inbox.vuxu.org
Subject: [PR PATCH] enable sixel in xterm
Date: Tue, 09 Jul 2019 06:30:32 +0200 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-12929@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 437 bytes --]
There is a new pull request by no-boot-device against master on the void-packages repository
https://github.com/no-boot-device/void-packages patch-1
https://github.com/void-linux/void-packages/pull/12929
enable sixel in xterm
my friend wanted to use sixel on their void linux install but it didn't have sixel in xterm so ¯\\\_(ã)_/¯
A patch file from https://github.com/void-linux/void-packages/pull/12929.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-patch-1-12929.patch --]
[-- Type: application/text/x-diff, Size: 1202 bytes --]
From ef21a1411194f7df51ec3ff4363c39c1fac8dead Mon Sep 17 00:00:00 2001
From: no-boot-device <nobootdevice@national.shitposting.agency>
Date: Mon, 8 Jul 2019 23:30:16 -0500
Subject: [PATCH] enable sixel in xterm
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
my friend wanted to use sixel on their void linux install but it didn't have sixel in xterm so ¯\_(ツ)_/¯
---
srcpkgs/xterm/template | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/srcpkgs/xterm/template b/srcpkgs/xterm/template
index fffe828fed4..a3df8bcfb6a 100644
--- a/srcpkgs/xterm/template
+++ b/srcpkgs/xterm/template
@@ -10,7 +10,7 @@ configure_args="--enable-wide-chars --enable-88-color --enable-broken-osc
--with-app-defaults=/usr/share/X11/app-defaults --enable-i18n
--disable-full-tgetent --disable-imake --enable-doublechars
--enable-freetype --enable-tcap-query --enable-logging --enable-dabbrev
- --with-pkg-config=yes --enable-exec-xterm --with-utempter"
+ --with-pkg-config=yes --enable-exec-xterm --with-utempter --enable-sixel"
hostmakedepends="pkg-config"
makedepends="libXaw-devel libXft-devel libutempter-devel libxkbfile-devel
ncurses-devel"
next reply other threads:[~2019-07-09 4:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-09 4:30 voidlinux-github [this message]
2019-07-09 16:24 ` voidlinux-github
2019-07-09 16:24 ` [PR PATCH] [Closed]: " voidlinux-github
2019-07-09 16:57 ` voidlinux-github
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-12929@inbox.vuxu.org \
--to=voidlinux-github@inbox.vuxu.org \
--cc=ml@inbox.vuxu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).