public inbox for cygwin-xfree@sourceware.org
help / color / mirror / Atom feed
From: mathog <mathog@caltech.edu>
To: cygwin-xfree@cygwin.com
Subject: Re: Clipboard interaction issues - breaks after awhile
Date: Tue, 07 Oct 2014 16:25:00 -0000 [thread overview]
Message-ID: <8a2e3bc1a87d0511765a735f841d3fe5@saf.bio.caltech.edu> (raw)
In-Reply-To: <5433E72A.9070907@dronecode.org.uk>
On 07-Oct-2014 06:14, Jon TURNEY wrote:
>> It always overwrites the Xwin.0.log file when it starts. Is there
>> some
>> change we could make to this .bat script that would cause it to at
>> least
>> save one previous version?
>
> I guess you could add to the above something like:
>
> move C:\cygwin\var\log\XWin.0.log C:\cygwin\var\log\XWin.0.log.old
>
> but yes, there is actually some code in the server to do that, but
> it's not turned on in XWin for unknown reasons...
Good idea. Changed it to the following and tested. It keeps the last
two versions.
======================after this line
@echo off
set CYGXTOP=%~dp0
C:
chdir "%CYGXTOP%\var\log\xwin"
move XWin.0.log.1 XWin.0.log.2
move XWin.0.log XWin.0.log.1
chdir "%CYGXTOP%\bin"
start Xwin :0 -multiwindow
======================before this line
Regards,
David Mathog
mathog@caltech.edu
Manager, Sequence Analysis Facility, Biology Division, Caltech
--
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/
next prev parent reply other threads:[~2014-10-07 16:25 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-03 20:02 mathog
2014-10-07 13:14 ` Jon TURNEY
2014-10-07 16:25 ` mathog [this message]
-- strict thread matches above, loose matches on Subject: below --
2014-09-10 16:33 Nem W Schlecht
2014-09-10 17:17 ` mathog
2014-09-10 17:57 ` Nem W Schlecht
2014-09-10 18:34 ` mathog
2014-09-10 21:23 ` Nem W Schlecht
2014-09-19 13:46 ` Jon TURNEY
2014-09-19 13:53 ` Nem W Schlecht
2014-09-26 14:45 ` Jon TURNEY
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=8a2e3bc1a87d0511765a735f841d3fe5@saf.bio.caltech.edu \
--to=mathog@caltech.edu \
--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).