From: PrinceKael <PrinceKael@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: jwm-2.4.1 broken fonts and not maximizing?
Date: Sat, 05 Mar 2022 22:51:26 +0100 [thread overview]
Message-ID: <20220305215126.EsbIFVkDskgM_7SxocqwHSPzaslKiIoMN84rK4zom2M@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-35962@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 884 bytes --]
New comment by PrinceKael on void-packages repository
https://github.com/void-linux/void-packages/issues/35962#issuecomment-1059836516
Comment:
Thanks mate i just panicked and I'm a bit of a newb.ie. I appreciate the link, I went into system.jwmrc and:
1. Went to all the font groups and changed from some "Sans-9" to my ideal font `` "-adobe-helvetica-bold-r-normal-*-14-*-*-*-*-*-iso10646-*``
2. Then I added a group for for ``<Option>nomaxborder</Option>``
which altogether 'fixed' my issue and brought back my settings some thing a lot more usable. ``jwm -p`` isn't ruturning any errors now apart from some "Segmentation fault" but at least now it looks clean and I've set things up better.
It seems an update just changed things from my usual set-up. I'll change anything else as needed but it's now close enough to what wanted originally, so thanks for the links.
next prev parent reply other threads:[~2022-03-05 21:51 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-04 13:14 [ISSUE] " PrinceKael
2022-03-04 17:09 ` tibequadorian
2022-03-04 17:27 ` tibequadorian
2022-03-05 21:51 ` PrinceKael [this message]
2022-03-05 21:52 ` PrinceKael
2022-03-05 21:53 ` PrinceKael
2022-03-05 21:54 ` PrinceKael
2022-03-06 11:23 ` [ISSUE] [CLOSED] " paper42
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=20220305215126.EsbIFVkDskgM_7SxocqwHSPzaslKiIoMN84rK4zom2M@z \
--to=princekael@users.noreply.github.com \
--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).