> "Abdelrazak" == Abdelrazak Younes <[EMAIL PROTECTED]> writes:
Abdelrazak> This is Jean-Marc new stuff AFAIK.
I'll have a look.
JMarc
Bo Peng a écrit :
> So, the lyxrc.defult is OK after initial configuration, then what do
> you see in the preference dialog, do you see auto?
The first time no, the viewer section says "yap" for DVI and is empty
for all other File formats. After a restart (without reconfiguring), the
viewer ed
On Tue, May 02, 2006 at 05:50:27PM +0200, Abdelrazak Younes wrote:
> Abdelrazak Younes a écrit :
> >Bo Peng a écrit :
> >>>Apparently they won't be set correctly as I need to reconfigure
> >>>after an
> >>>initial startup. See my previous mail.
> >>
> >>That was exactly what puzzled me. I do not h
> So, the lyxrc.defult is OK after initial configuration, then what do
> you see in the preference dialog, do you see auto?
The first time no, the viewer section says "yap" for DVI and is empty
for all other File formats. After a restart (without reconfiguring), the
viewer edit box contains aut
Bo Peng a écrit :
> 3. DO WE SEE auto in $HOME/.lyx/lyxrc.default?
yes I think, there are "auto" "" see attached. Also attached the same
file after reconfigure.
So, the lyxrc.defult is OK after initial configuration, then what do
you see in the preference dialog, do you see auto?
The first tim
> 3. DO WE SEE auto in $HOME/.lyx/lyxrc.default?
yes I think, there are "auto" "" see attached. Also attached the same
file after reconfigure.
So, the lyxrc.defult is OK after initial configuration, then what do
you see in the preference dialog, do you see auto?
If you do see auto, and the men
Abdelrazak Younes a écrit :
Bo Peng a écrit :
Apparently they won't be set correctly as I need to reconfigure
after an
initial startup. See my previous mail.
That was exactly what puzzled me. I do not have a windows machine
here. And I (or you) need to see the result of
1. clear Application
Bo Peng a écrit :
Apparently they won't be set correctly as I need to reconfigure after an
initial startup. See my previous mail.
That was exactly what puzzled me. I do not have a windows machine
here. And I (or you) need to see the result of
1. clear Application Data/lyx
2. start lyx
I've d
Apparently they won't be set correctly as I need to reconfigure after an
initial startup. See my previous mail.
That was exactly what puzzled me. I do not have a windows machine
here. And I (or you) need to see the result of
1. clear Application Data/lyx
2. start lyx
3. DO WE SEE auto in $HOME/
Bo Peng a écrit :
But with a second reconfigure, I have now three PDF (dvipdfm, pdflatek,
ps2pdf) that all work! And I have a new View HTML; but this one doesn't
work because htlatex doesn't understand paths with space and the temp
directory is by default in the "c:/Document and Settings/bla bla
When I delete my user directory (in Application Data) and I restart LyX
from the console, I have the same bad behavior as I described (only DVI
and two PDF that don't work) but I can see at the console that LyX is
being reconfigured at startup. After a tool->Reconfigure, the functional
menus appea
But with a second reconfigure, I have now three PDF (dvipdfm, pdflatek,
ps2pdf) that all work! And I have a new View HTML; but this one doesn't
work because htlatex doesn't understand paths with space and the temp
directory is by default in the "c:/Document and Settings/bla bla bla"
directory. Thi
Abdelrazak Younes a écrit :
Abdelrazak Younes a écrit :
Bo Peng a écrit :
> Please test.
I have not tested it but with svn of three days ago, I have only
View->{DVI, PDF(dvipdfm), PDF{pdflatek)}, PS is not there (used to use
gsview). DVI works OK but both PDF don't (dialog saying "cannot view
Abdelrazak Younes a écrit :
Bo Peng a écrit :
> Please test.
I have not tested it but with svn of three days ago, I have only
View->{DVI, PDF(dvipdfm), PDF{pdflatek)}, PS is not there (used to use
gsview). DVI works OK but both PDF don't (dialog saying "cannot view
file", "No information to vie
I have the exact same behavior with your patch applied to revision 13788
(which contains related changes from JMarc AFAIU).
Please report your lyxrc.default, and I will see what my have gone wrong next.
Bo
Bo Peng a écrit :
> Please test.
I have not tested it but with svn of three days ago, I have only
View->{DVI, PDF(dvipdfm), PDF{pdflatek)}, PS is not there (used to use
gsview). DVI works OK but both PDF don't (dialog saying "cannot view
file", "No information to view PDF"). I have Acrobat Reade
Bo Peng a écrit :
> Please test.
I have not tested it but with svn of three days ago, I have only
View->{DVI, PDF(dvipdfm), PDF{pdflatek)}, PS is not there (used to use
gsview). DVI works OK but both PDF don't (dialog saying "cannot view
file", "No information to view PDF"). I have Acrobat Reade
> Please test.
I have not tested it but with svn of three days ago, I have only
View->{DVI, PDF(dvipdfm), PDF{pdflatek)}, PS is not there (used to use
gsview). DVI works OK but both PDF don't (dialog saying "cannot view
file", "No information to view PDF"). I have Acrobat Reader 7 installed
and F
Bo Peng a écrit :
I tested this last patch on Cygwin and it does not work well.
Specifically I have to delete /lyxrc.defaults otherwise I
only get "PDF (dvipdfm)" and "PDF (pdflatex)" in the View menu.
I finally have my mingw+lyx+qt4 set up and can test this patch.
Very good, may I asked whic
On Mon, May 01, 2006 at 12:50:22PM -0500, Bo Peng wrote:
> > I understand, but they are exactly the same: only QTDIR changes ;-)
> > please, compare lyconfig-x11 (used for the standalone qt3) and
> > lyxconfig-qt3-x11 (which I wrote for the cygwin qt3).
>
> At least cygwin/qt3 relies on cygwin1.d
I understand, but they are exactly the same: only QTDIR changes ;-)
please, compare lyconfig-x11 (used for the standalone qt3) and
lyxconfig-qt3-x11 (which I wrote for the cygwin qt3).
At least cygwin/qt3 relies on cygwin1.dll, standalone qt3 does not.
I will try your approach after my downgrad
On Mon, May 01, 2006 at 12:25:52PM -0500, Bo Peng wrote:
> > Yes, and I can also test it with my home grown qt3. Why don't you try
> > to build qt3 following http://wiki.lyx.org/LyX/LyXOnCygwin ?
>
> I was afraid of the potential configuration/link differences between
> cygwin/qt3 and standalone
Yes, and I can also test it with my home grown qt3. Why don't you try
to build qt3 following http://wiki.lyx.org/LyX/LyXOnCygwin ?
I was afraid of the potential configuration/link differences between
cygwin/qt3 and standalone qt3.
Then, what you do with this qt3 you simply redo it with the cyg
On Mon, May 01, 2006 at 11:25:54AM -0500, Bo Peng wrote:
> > That won't work as they don't take into account older releases, so the
> > package must work with what is current. I think that we have to wait
> > a new release of the cygwin dll which should be imminent for what I
> > read in their mai
That won't work as they don't take into account older releases, so the
package must work with what is current. I think that we have to wait
a new release of the cygwin dll which should be imminent for what I
read in their mailing list.
I know. But as you may have long noticed, I am not a patient
On Mon, May 01, 2006 at 09:10:09AM -0500, Bo Peng wrote:
> > I have changed again the cygwin part. After thinking about it I moved
> > the code syncing the cygwin and windows environment to os::init,
> > where IMO it belongs.
>
> I hope that this one is the last one for this patch. Otherwise, Lar
I have changed again the cygwin part. After thinking about it I moved
the code syncing the cygwin and windows environment to os::init,
where IMO it belongs.
I hope that this one is the last one for this patch. Otherwise, Lars
(or whoever it may concern) will never look at this patch seriously
an
On Sun, Apr 30, 2006 at 10:20:27PM -0500, Bo Peng wrote:
> >
> > I am returning your patch with a small enhancement to the cygwin part.
>
> Not a problem. I will apply your modifications as well.
I have changed again the cygwin part. After thinking about it I moved
the code syncing the cygwin a
That is probably the homegrown file type recognition in
lyx::support::getFormatFromContents() recognizing OOo files as zip. This
is not surprising since they are indeed zipped, but something has to be
done here.
i do not know much about OO and the conversion processes. I have added
a fs::exists(
Am Montag, 1. Mai 2006 01:57 schrieb Bo Peng:
> I am not sure this is related to this patch. I installed openoffice 2
> and I have the same error message. I then look at the file, it does
> not exist! Instead, I get a directory and two sub folders, with a
> message on the console saying "zip is no
I am returning your patch with a small enhancement to the cygwin part.
Not a problem. I will apply your modifications as well.
Bo
On Sun, Apr 30, 2006 at 07:54:22PM -0500, Bo Peng wrote:
> This is in the attached updated patch. Allow me to reiterate what
> this patch does:
>
> Under windows (including cygwin):
>
> 1. configure.py does not actually search for programs. %% is replaced
> by 'auto'.
>
> 2. A viewer item unde
Although this is unrelated to my patch, I will add a fs::exists check
in view() function to make the error message clearer.
This is in the attached updated patch. Allow me to reiterate what
this patch does:
Under windows (including cygwin):
1. configure.py does not actually search for program
Only a minor glitch: I was missing the "OpenOffice.Org Writer" entry
in the View menu, so I added "auto" as a viewer in preferences for
this format. I obtained an entry in the View menu but after choosing
this entry a dialog popped out saying that it failed.
However, after quitting and restarting
On Sun, Apr 30, 2006 at 02:55:18PM -0500, Bo Peng wrote:
> > I tested this last patch on Cygwin and it does not work well.
> > Specifically I have to delete /lyxrc.defaults otherwise I
> > only get "PDF (dvipdfm)" and "PDF (pdflatex)" in the View menu.
>
> I finally have my mingw+lyx+qt4 set up a
I tested this last patch on Cygwin and it does not work well.
Specifically I have to delete /lyxrc.defaults otherwise I
only get "PDF (dvipdfm)" and "PDF (pdflatex)" in the View menu.
I finally have my mingw+lyx+qt4 set up and can test this patch. (Poor
ghostview gets installed/uninstalled five
On Sun, Apr 30, 2006 at 10:26:32AM -0500, Bo Peng wrote:
> > > This is weird to me. Any idea? Do you see "auto" in lyxrc.default
> > > after reconfiguration?
>
> The lyxrc.default is correct.
>
> > sh: auto: command not found
>
> That may be a bug of detecting exit value from ShellExecute. I wi
> This is weird to me. Any idea? Do you see "auto" in lyxrc.default
> after reconfiguration?
The lyxrc.default is correct.
sh: auto: command not found
That may be a bug of detecting exit value from ShellExecute. I will check.
printed on the terminal and then Acrobat5 is used for showing th
On Sun, Apr 30, 2006 at 05:08:23PM +0200, Enrico Forestieri wrote:
> I attach here the lyxrc.defaults produced by Tools->Reconfigure.
I forgot to do that.
--
Enrico
# This file has been automatically generated by LyX' lib/configure.py
# script. It contains default settings that have been determ
On Sun, Apr 30, 2006 at 09:46:13AM -0500, Bo Peng wrote:
> > I tested this last patch on Cygwin and it does not work well.
> > Specifically I have to delete /lyxrc.defaults otherwise I
> > only get "PDF (dvipdfm)" and "PDF (pdflatex)" in the View menu.
>
> That is the design. Use the old lyxrc.de
I tested this last patch on Cygwin and it does not work well.
Specifically I have to delete /lyxrc.defaults otherwise I
only get "PDF (dvipdfm)" and "PDF (pdflatex)" in the View menu.
That is the design. Use the old lyxrc.default, '' will be there for
not-found viewers and lyx will not do anythi
On Fri, Apr 28, 2006 at 11:57:22PM -0500, Bo Peng wrote:
> Attached is a modified patch that
>
> 1. in configure.py, under windows/cygwin, %% is replaced by auto.
> Programs are not actually checked. ( so no waste of time)
>
> checkFormatEntries(os.name != 'nt' and sys.platform != 'cygwin')
>
Attached is a modified patch that
1. in configure.py, under windows/cygwin, %% is replaced by auto.
Programs are not actually checked. ( so no waste of time)
checkFormatEntries(os.name != 'nt' and sys.platform != 'cygwin')
2. in graph.c, the logic is:
+ if (!only_viewable || form
Who agreed to that? Why not have a format function for Windows that doesn't
check for anything at all but just outputs a sane selection of formats (with
prettynames).
No, we want to allow users to set viewers explicitly. The system
should set viewers to "" or "auto' and allow users to set them t
Bo Peng <[EMAIL PROTECTED]> writes:
> With my patch, the viewers, formats are most of the time
> non-informative under windows. (We even lose prettyname). That is why
> I suggest hiding the panel (at a cost of not able to specify viewer.)
> Now, we agreed to have
> \format ps postscript "" "" ""
>
> Formats aren't viewers. Formats should stay, or how would you define
> conversion chains from format XYZ to format PNG?
And even if they were: The agreement was that windows viewers should be used
when possible, but that users should still be able to define their own in
LyX.
With my patch, th
Angus Leeming wrote:
> Bo Peng <[EMAIL PROTECTED]> writes:
>> I would suggest that we remove the format panel in the preference
>> dialog under windows.
>
> Formats aren't viewers. Formats should stay, or how would you define
> conversion chains from format XYZ to format PNG?
And even if they we
Bo Peng <[EMAIL PROTECTED]> writes:
> I would suggest that we remove the format panel in the preference
> dialog under windows.
Formats aren't viewers. Formats should stay, or how would you define conversion
chains from format XYZ to format PNG?
Angus
48 matches
Mail list logo
