licitly set to "keep". This is counterintutitive. Said that, I'd better wait a bit for an
xpdf version in the standard cygwin repository. Reason: I do not want to update biber-related stuff from
anywhere except standard cygwin repository since it's production-critical for me
Ken wrote:
On 5/13/2016 9:26 PM, Jaakov Jaakov wrote:
(/usr/share/texmf-dist/tex/latex/fontspec/fontspec.cfg)))kpathsea:make_tex:
Invalid fontname `TeX Gyre Termes', contains ' '
!
! fontspec error: "font-not-found&quo
Volker wrote:
Ken Brown writes:
> On 5/14/2016 6:56 AM, Jaakov Jaakov wrote:
>> This rebasement does not seem to survive updates or reinstalls. I know
>> that rebasement is difficult, but still, could you, perhaps, solve it in
>> a more long-term way?
&g
, solve it in a more
long-term way?
Thanks in advance,
Jaakov
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
How to reproduce:
[
user@host:~$ cp -a /usr/share/texmf-dist/doc/fonts/tex-gyre-math /tmp/test
user@host:~$ cd /tmp/test
user@host:/tmp/test$ xelatex test-xelatex-texgyre_termes_math
This is XeTeX, Version 3.14159265-2.6-0.2 (TeX Live 2015/Cygwin) (preloaded
format=xelatex)
restricted \writ
Dear Mark:
After rebooting and starting a fresh non-X terminal, rebasing worked. xpdf
starts again. Thanks!
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://c
min None 0 15. Aug 2015 ..
drwxr-xr-x+ 1 admin None 0 17. Apr 22:23 bin
...
As we see, the write attributes for "admin" are set, and I am "admin"
Best regards,
Jaakov
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin
Finally I got the culprit machine again.
Sorry but my suspicion expressed earlier, that there's an address
collision, was incorrect. The rebase source code shows it's a Windows
error code being reported, and it's Windows' ReBaseImage64() function
itself having some issue operating on t
> Do you have write access to that file and its directory?
At this very moment, I have no more the access to the particular
machine. But I'll check again, though this is unlikely to happen this week.
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.
Mark, thanks!
But, unfortunately:
/usr/bin$ rebase --base=0xf730 cygXt-6.dll
ReBaseImage (/usr/bin/cygXt-6.dll) failed with last error = 6
rebase -i *.dll outputs no stars at all (see the attachment).
Is there, perhaps, a chance for a permanent solution?/usr/bin/cyglsa64.dll
Same bug for me.
$ xpdf &
[1] 3496
$ Cygwin runtime failure: /usr/bin/xpdf.exe: Invalid relocation. Offset
0x2f6eabad9 at address 0x100494523 doesn't fit into 32 bits
But Mark's suggestion doesn't work:
[1]+ Exit 127xpdf
/usr/bin$ rebase -i cygXt*
/usr/bin/cygXtst-6.dll
> On 2/23/2016 3:42 PM, Jaakov wrote:
>Ken, I'll try your file, thanks a lot!
>But let us recapitulate that such files get outdated very quickly.
> Your best defense against this is to read the xinit release
> announcements. You can always ask for help if you want
Ken, I'll try your file, thanks a lot!
But let us recapitulate that such files get outdated very quickly.
Frankly speaking, I would be most probably lost when in need to adapt
some part of your file.
(E.g., the documentation
http://x.cygwin.com/docs/man1/startxwin.1.html
from January 28, 2016
...
And yet a third alternative would be to automatically install a default
$HOME/.startxwinrc during updates.
...
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: ht
Ah, perhaps. There may be ways to catch that, but it may be easier for the
OP to copy the startxwinrc file's contents. Not the best for responding to
future changes ...
One way to prevent recursion is
if [[ "$FILEINCLUDED" != "1" ]];
then
export FILEINCLUDED=1
... # do real job here
fi
Why not do:
xterm ... &
/etc/X11/xinit/startxwinrc
?
Where do you suggest to do it?
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#u
> Dear Marco:
>
> So, are you saying that not starting xterm is by design?
yes
Well, then, apparently, the design changed several months ago.
>> http://x.cygwin.com/docs/man1/startxwin.1.html
>
> The manpage above is a bit outdated; creating a .startxwinrc with
>
> xrdb -load $HOME/.Xresou
in front of -profile leads to two xterm windows.
However, there are lots of other errors on the console. Said that, what would
be an appropriate .startxwinrc or /etc/X11/xinit/startxwinrc for getting one
(not two) xterm? Better, one uxterm?
Best,
Jaakov.
--
Problem reports: http://cygwin
attached in my case; it can be sent it to a private e-mail
address if asked.)
Any help? Thanks in advance,
Jaakov.
PS. Below is the output of startxwin from a cygwin text terminal:
Welcome to the XWin X Server
Vendor: The Cygwin/X Project
Release: 1.18.1.0
OS: CYGWIN_NT-6.3 dell_vostro 2.4.1(0.293
Jaakov Jaakov writes:
> Regarding run 1.3.3-1,
Is there any reason why you're still bothering with 1.3.3 and not trying 1.3.4?
Hi Achim and Jon:
Several minites ago I've tried run 1.3.4-1. (Previously, I expected getting and
using a test version to be much harder than it actual
once in a long row of attempts).
According to the Task Manager, the run process shortly appears and then disappears in one-two seconds. No other effects, except some disc activity, are visible. (In particular, XWin doesn't start.)
\var\log\xwin remains untouched.
Jaakov.
--
Problem repo
sr/bin/bash.exe -l -c "cd; /usr/bin/startxwin"
from cygwin64 text console (mintty with some arguments) does start an Xwin
Server. (Xterm has to be started separately afterwards, but let's hope that
this is a different issue.)
Best,
Jaakov.
--
Problem reports: http:
Jaakov Jaakov writes:
>XWin fails to start again (previously reported half a year ago or so).
>
>The command issued by a shortcut is
>C:\cygwin64\bin\run.exe --quote /usr/bin/bash.exe -l -c "cd;
/usr/bin/startxwin"
Can you reproduce this when running the same command f
XWin fails to start again (previously reported half a year ago or so).
The command issued by a shortcut is
C:\cygwin64\bin\run.exe --quote /usr/bin/bash.exe -l -c "cd; /usr/bin/startxwin"
Upon starting the shortcut, there is some disc acitivty, but no window opens,
and no XWin processes show up
starting, I'll report again.
Best regards,
Jaakov.
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
While executing the command "Xwin Server" from Windows 8.1, the server
won't start. Apparently, the executed command is
C:\cygwin64\bin\run.exe --quote /usr/bin/bash.exe -l -c "cd;
/usr/bin/startxwin"
The file C:\cygwin64\run.exe.stackdump is produced. Instead I expect,
however, an X server proc
emoval of the C:\cygwin64 directory and reinstalling did not help.
Afterwards, reinstalling xinit did not help.
This issue persists for a few months already. Last year, XWin started without
problems.
Any help?
(I tried to add attachments, but somehow the e-mails do not appear on the
cy
Dear all:
While executing the command "Xwin Server" from Windows 8.1, the server won't
start. Apparently, the executed command is
C:\cygwin64\bin\run.exe --quote /usr/bin/bash.exe -l -c "cd; /usr/bin/startxwin"
The file C:\cygwin64\run.exe.stackdump is produced. Instead I expect, however,
an
For an unknown reason,
svn help
as well as other commands of subversion work again after an update yesterday.
Whoever contributed to repairing, thanks a lot!
Jaakov.
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation
log
had not segfaulted, but had ran forever, having been continuously enlarging /tmp/svn.log
with some repeated "...leave..." message. Now the command does segfault,
producing the output mentioned in a previous e-mail.
Jaakov
--
Problem reports: http://cygwin.com/problems.html
FAQ:
latest snapshot. See [1].
[1] http://cygwin.com/ml/cygwin/2013-12/msg00294.html
Thank you, Jon. Indeed, my relatively recent cygwin (as of today) does not have
this patch yet. Let us wait until the snapshot gets released.
Best,
Jaakov.
--
Problem reports: http://cygwi
, and
then x^2, the after-dot-digits would be considered again.
Please fix the bug!
Best regards,
Jaakov
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin
32 matches
Mail list logo