public inbox for cygwin-xfree@sourceware.org
help / color / mirror / Atom feed
From: "Yaakov (Cygwin/X)" <yselkowitz@users.sourceforge.net>
To: cygwin-xfree@cygwin.com
Subject: Re: Implement ~/.xsession-errors?
Date: Tue, 27 Nov 2012 07:03:00 -0000	[thread overview]
Message-ID: <1353999800.892.17.camel@YAAKOV04> (raw)
In-Reply-To: <50B3B660.2050403@cornell.edu>

On Mon, 2012-11-26 at 13:35 -0500, Ken Brown wrote:
> I'm wondering whether it's feasible for the Cygwin X-server to redirect 
> stderr to ~/.xsession-errors for programs started under the server, as 
> is done on some Linux systems.  This would be useful for two reasons. 
> First, some programs emit warnings that can be ignored, and it would be 
> nice if users could avoid seeing those every time they start the 
> program.  Second, and more importantly, standard error is often lost, 
> for instance for programs started by ~/.startxwinrc.  It could be useful 
> for package maintainers to be able to ask users to send the contents of 
> ~/.xsession-errors.

~/.xsession-errors is a GDM-ism; as we don't use DMs in Cygwin/X, it
would mean implementing it from scratch somewhere else.  Also, a quick
Google search turned up a bunch of bugs about this file continuously
growing to the point of filling the disk partition, which is obviously
unacceptable, nor would it be helpful in the way you propose (think:
strace snippets).  So I would say, probably not.  If you want to see
errors from a particular program, just start it from console, copy and
paste.


Yaakov
Cygwin/X



--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://x.cygwin.com/docs/
FAQ:                   http://x.cygwin.com/docs/faq/


      reply	other threads:[~2012-11-27  7:03 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-26 18:35 Ken Brown
2012-11-27  7:03 ` Yaakov (Cygwin/X) [this message]

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=1353999800.892.17.camel@YAAKOV04 \
    --to=yselkowitz@users.sourceforge.net \
    --cc=cygwin-xfree@cygwin.com \
    /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 read-only IMAP folder(s) and NNTP newsgroup(s).