mailing-list for TeXmacs Users

[Guillaume Andrieu <address@hidden>]

For the moment, I test texmacs under VMWARE and mandriva one, which is 
quite up to date with Texmacs versions apparently. The performances are 
good with a Core2duo, and it is quite simple for people who don't know a 
lot about cygwin and compilling. But I noticed a bug of Texmacs with 
Mandriva with french accentued characters while displaying directories 
and working with ispell french dictionnary... the "é" becomes someting 
like "~Eà".


Robert Ransom a écrit :
> Guillaume Andrieu wrote:
> > Thanks for answers.
> > While searching on google, it seems that lots of vista users are 
> > experiencing problems with cygwin and other "linux-windows" tools due 
> > to restrictions in vista
> > Apparently, a virtual machine as VMWARE is the only solution to make 
> > texmacs work under vista.
> The version of TeXmacs (1.0.6) installed by Cygwin Setup works for me 
> on a Vista Home Basic system - start Cygwin/X, then start a Cygwin 
> shell, set the environment variable DISPLAY to ":0", and run 
> "texmacs".  Newer versions of TeXmacs should work, but you will 
> probably need to compile them yourself.
> > The message with Cygtexmacs is the following : "A fatal error has 
> > occured and Cygwin/X will now exit".
> >
> > The log is :
> >
> > _XSERVTransmkdir: ERROR: euid != 0,directory /tmp/.X11-unix will not 
> > be created.
> > (II) XF86Config is not supported
> > (II) See http://x.cygwin.com/docs/faq/cygwin-x-faq.html for more 
> > information
> > winAdjustVideoModeShadowGDI - Using Windows display depth of 32 bits 
> > per pixel
> > winAllocateFBShadowGDI - Creating DIB with width: 1600 height: 1200 
> > depth: 32
> > winInitVisualsShadowGDI - Masks 00ff0000 0000ff00 000000ff BPRGB 8 d 
> > 24 bpp 32
> > null screen fn ReparentWindow
> > null screen fn RestackWindow
> > InitQueue - Calling pthread_mutex_init
> > InitQueue - pthread_mutex_init returned
> > InitQueue - Calling pthread_cond_init
> > InitQueue - pthread_cond_init returned
> > winInitMultiWindowWM - Hello
> > winMultiWindowXMsgProc - Hello
> > winInitMultiWindowWM - Calling pthread_mutex_lock ()
> > winMultiWindowXMsgProc - Calling pthread_mutex_lock ()
> > MIT-SHM extension disabled due to lack of kernel support
> > XFree86-Bigfont extension local-client optimization disabled due to 
> > lack of shared memory support in the kernel
> > (--) Setting autorepeat to delay=500, rate=31
> > (--) winConfigKeyboard - Layout: "0000040C" (0000040c)
> > (--) Using preset keyboard for "French (Standard)" (40c), type "4"
> > (--) 3 mouse buttons found
> > Could not init font path element /usr/X11R6/lib/X11/fonts/TTF/, 
> > removing from list!
> > Could not init font path element /usr/X11R6/lib/X11/fonts/Type1/, 
> > removing from list!
> > Could not init font path element /usr/X11R6/lib/X11/fonts/CID/, 
> > removing from list!
> > Could not init font path element /usr/X11R6/lib/X11/fonts/75dpi/, 
> > removing from list!
> > Could not init font path element /usr/X11R6/lib/X11/fonts/100dpi/, 
> > removing from list!
> > winInitMultiWindowWM - pthread_mutex_lock () returned.
> > winInitMultiWindowWM - pthread_mutex_unlock () returned.
> > winMultiWindowXMsgProc - pthread_mutex_lock () returned.
> > winInitMultiWindowWM - DISPLAY=127.0.0.1:0.0
> > winMultiWindowXMsgProc - pthread_mutex_unlock () returned.
> > winMultiWindowXMsgProc - DISPLAY=127.0.0.1:0.0
> > winProcEstablishConnection - Hello
> > winInitClipboard ()
> > winProcEstablishConnection - winInitClipboard returned.
> > winClipboardProc - Hello
> > DetectUnicodeSupport - Windows NT/2000/XP
> > winClipboardProc - DISPLAY=127.0.0.1:0.0
> > winInitMultiWindowWM - XOpenDisplay () returned and successfully 
> > opened the display.
> > winMultiWindowXMsgProc - XOpenDisplay () returned and successfully 
> > opened the display.
> > winClipboardProc - XOpenDisplay () returned and successfully opened 
> > the display.
> > winDeinitMultiWindowWM - Noting shutdown in progress
> > winClipboardProc - winClipboardFlushWindowsMessageQueue trapped 
> > WM_QUIT message, exiting main loop.
> > winClipboardProc - XDestroyWindow succeeded.
> >
> > winClipboardIOErrorHandler!
> These are Cygwin/X messages, not TeXmacs messages.  The URL in the 
> third line of this sequence of messages points to a FAQ list for 
> Cygwin/X with a section on "Error and Warning Messages"; since both 
> the 75 DPI and 100 DPI font directories seem to be missing or 
> unusable, you probably need to follow the instructions in section 8.4 
> ("Fatal server error: could not open default font 'fixed'") of the FAQ.
>
> Robert Ransom