Github messages for voidlinux
 help / color / mirror / Atom feed
From: reedts <reedts@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [ISSUE] lightdm Xsession: is xrdb "-nocpp" option necessary?
Date: Wed, 03 Nov 2021 11:25:07 +0100	[thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-33876@inbox.vuxu.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 1261 bytes --]

New issue by reedts on void-packages repository

https://github.com/void-linux/void-packages/issues/33876

Description:
While investigating some strange problems on xsession startup using lightdm + i3, I found this line in `/etc/lightdm/Xsession` and was wondering whether the `-nocpp` option is used here for a specific reason: [see here](https://github.com/void-linux/void-packages/blob/a279abf769ef7cab6ebb49d8c99bf774a2ff97b8/srcpkgs/lightdm/files/xsession#L19)

As an example from the archlinux package sources for lightdm: they're omitting the `-nocpp` option (see [here](https://github.com/archlinux/svntogit-packages/blob/8d85fa6b8d07e4a82b24efc7635853110c2f93ed/trunk/Xsession#L19))

Furthermore, having a look at xrdb's source code, you can see [here](https://gitlab.freedesktop.org/xorg/app/xrdb/-/blob/master/xrdb.c#L917) that xrdb should correctly check for the existence of the default cpp preprocessor (`/usr/lib/cpp`) and automatically disables preprocessing of `.Xresources` if the binary cannot be found.

So, in my opinion it should be safe omitting `-noccp` in the global `/etc/lightdm/Xsession` script and would simultaneously allow the user to have their `.Xresources` preprocessed on session-startup if a preprocessor can be found.

             reply	other threads:[~2021-11-03 10:25 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-03 10:25 reedts [this message]
2021-11-03 19:40 ` mtboehlke
2021-11-03 19:48 ` mtboehlke
2021-11-03 19:49 ` mtboehlke
2021-11-03 21:25 ` mtboehlke
2022-06-10  2:14 ` github-actions
2022-06-24  2:15 ` [ISSUE] [CLOSED] " github-actions

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-33876@inbox.vuxu.org \
    --to=reedts@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).