This fix is needed to use dual-width fonts, which have double-width
glyphs (e.g. CJK unified ideographs).
Signed-off-by: Ryusei Yamaguchi
---
config.def.h | 8
st.c | 8 +++-
2 files changed, 15 insertions(+), 1 deletion(-)
diff --git a/config.def.h b/config.def.h
index fd0
On Mon, Mar 07, 2016 at 10:18:12PM +0100, Ton van den Heuvel wrote:
> The y-position of a character found by asking fontconfig for a matching
> font does not take the border pixels into account, resulting in a
> slightly misaligned vertical position.
>
> Signed-off-by: Ton van den Heuvel
> ---
>
To illustrate this, have a look at the 'branch' character before:
http://i.imgur.com/ymuPXAm.png ...and after:
http://i.imgur.com/f2J2Ozs.png
Ton
On Mon, Mar 7, 2016 at 10:18 PM, Ton van den Heuvel
wrote:
> The y-position of a character found by asking fontconfig for a matching
> font does not t
The y-position of a character found by asking fontconfig for a matching
font does not take the border pixels into account, resulting in a
slightly misaligned vertical position.
Signed-off-by: Ton van den Heuvel
---
st.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/st.c b/s
On Mon, 7 Mar 2016 20:03:17 +0100
wrote:
> Hi,
>
> > I'm thinking about removing support for all
> > output formats except unified context from
> > my diff(1) candidate. I want to hear your
> > opinion.
>
> I don't like the idea at all. I use some times
> the ed output for some scripts. SCCS,
Greetings.
On Mon, 07 Mar 2016 20:52:30 +0100 Ryusei Yamaguchi wrote:
> On 2016/03/07 22:53, Christoph Lohmann wrote:
> > Please give me more context, like a screenshot before and after and why this
> > can't be fixed in fontconfig itself. This would be yet another fontconfig
> > API
> > hack in
Hi,
> I'm thinking about removing support for all
> output formats except unified context from
> my diff(1) candidate. I want to hear your
> opinion.
I don't like the idea at all. I use some times
the ed output for some scripts. SCCS, RCS and
CVS use it to, so I think it is a very bad idea
to rem
On Mon, Mar 7, 2016 at 4:04 PM, Eon S. Jeon wrote:
> Hello,
>
> My obsession for transparency never knows when to stop, so I couldn't resist
> writing this patch.
>
> This patch allows dwm to have translucent bars, while keeping all the text on
> it opaque, just like my ARGB patch for st[1].
>
> T
Will do, thanks for including the change!
On Mon, Mar 7, 2016 at 2:33 PM, Christoph Lohmann <2...@r-36.net> wrote:
> Greetings.
>
> On Mon, 07 Mar 2016 14:33:54 +0100 Ton van den Heuvel
> wrote:
>> In case anything gets drawn in drawregion, xdrawglyphfontspecs ensures
>> that the region that nee
On 2016/03/07 22:53, Christoph Lohmann wrote:
Please give me more context, like a screenshot before and after and why this
can't be fixed in fontconfig itself. This would be yet another fontconfig API
hack in st.
Step to Reproduce:
1. Install M+ 1m from https://osdn.jp/projects/mplus-fonts/re
Hello,
My obsession for transparency never knows when to stop, so I couldn't resist
writing this patch.
This patch allows dwm to have translucent bars, while keeping all the text on
it opaque, just like my ARGB patch for st[1].
The patch also allows changing the opacity of borders, but it only
Heyhey
On Mon, Mar 7, 2016 at 7:06 AM, Ryusei Yamaguchi wrote:
> This fix is needed to use dual-width fonts, which have double-width
> glyphs (e.g. CJK unified ideographs).
>
> Signed-off-by: Ryusei Yamaguchi
> ---
> st.c | 15 ++-
> 1 file changed, 14 insertions(+), 1 deletion(-)
Greetings.
On Mon, 07 Mar 2016 14:53:50 +0100 Ryusei Yamaguchi wrote:
> This fix is needed to use dual-width fonts, which have double-width
> glyphs (e.g. CJK unified ideographs).
Please give me more context, like a screenshot before and after and why this
can't be fixed in fontconfig itself. Th
Greetings.
On Mon, 07 Mar 2016 14:33:54 +0100 Ton van den Heuvel
wrote:
> In case anything gets drawn in drawregion, xdrawglyphfontspecs ensures
> that the region that needs to be drawn to is cleaned up. In case this
> patch is not accepted; the current code contains an issue;
>
> -xter
On Mon, 7 Mar 2016 12:23:07 +0100
Mattias Andrée wrote:
Waidmannsheil, Mattias,
> I'm thinking about removing support for all
> output formats except unified context from
> my diff(1) candidate. I want to hear your
> opinion.
> -f
> -e
> (no flag)
> -c
> Unified context is also the eas
Ahoy comrades!
I'm thinking about removing support for all
output formats except unified context from
my diff(1) candidate. I want to hear your
opinion.
This means removal of:
-f
ed-like diff-script that cannot be parsed
for patch(1). It is intended to be easier
for humans to read
16 matches
Mail list logo