Kornel Benko wrote:
> OK, so may I change runtests.py again? If yes, when?
IMO Yes, but I can't answer the when question
Georg
Scott Kostyshak wrote:
> Bisect leads me here:
> c14b9e67
Thanks, I'll have a look.
Georg
Daniel Vainsencher wrote:
> Update:
> I have found that my current examples for "macros that are lost"
> are all explained (and fixed) by movement between the preamble and
> the document. That is, at some point they moved above the
> \begin{document} in the latex, I wou
Daniel Vainsencher wrote:
>> I think the second one is doable as well. Ideally, a local layout (or
>> module) would be generated for all unknown commands and environments. The
>> needed infrastructure is all in place: you can define new known commands
>> in tex2lyx during runtime, and since very r
Richard Heck wrote:
> On 06/05/2013 05:17 AM, Daniel Vainsencher wrote:
>> Hi again Georg, everyone,
>>
>> Thank you for your answers, I'd missed this one. Since my requests did
>> not recruit any GSOC love, I'm looking into it myself. I hope you can
>> help me get started.
Definitely. I may some
Scott Kostyshak wrote:
> I remember a lot of work was done on improving pasting (e.g. LaTeX
> detection) but I don't remember this change being discussed.
>
> Before (and now on current 2.0git), you could copy a png from the web
> (coyping in Chromium on Ubuntu stores it as MIME type "image/bmp"
Kornel Benko wrote:
> Am Mittwoch, 5. Juni 2013 um 13:12:32, schrieb Vincent van Ravesteijn
>>
>> Do you really expect us to do this manual work for every temporary state:
>> 2.1.0dev, 2.1.0beta1, 2.1.0dev, 2.1.0beta2, 2.1.0dev, 2.1.0rc1, 2.1.0dev,
>> 2.1.0rc2, 2.1.0dev, 2.1.0, 2.2.0dev, 2.1.0dev
Kornel Benko wrote:
> Am Sonntag, 2. Juni 2013 um 13:27:24, schrieb Jürgen Spitzmüller
>
>> Kornel Benko wrote:
>> > Missing initial values in stdcounters.inc
>> >
>> > E.g.
>> > Counter chapter
>> > InitialValue 1
>> > PrettyFormat "Chapter ##"
>> >
Uwe Stöhr wrote:
> I miss a guide of how "old" a feature must be to be added to a layout file
> in branch for example.
IIRC we don't have an agreement on this. My personal opinion:
A new command/environment which translates 1:1 into a style may be as new as
you like (if it is officially release
Uwe Stöhr wrote:
> Am 01.06.2013 13:52, schrieb Stephan Witt:
>
>> But the documentation in filetools.h clearly states for quote_python:
>> /*
>> Quote for python. Use this if you want to store a filename in a python
>> script. Example: os << "infile = " << quoteName(filename) << '\\n';
>> */
>>
Stephan Witt wrote:
> I tried this and it's ok. Thanks.
Thanks from me as well, I forgot to change that file.
Georg
Uwe Stöhr wrote:
> Am 30.05.2013 20:35, schrieb Georg Baum:
>
>> This is not true anymore. I implemented a mechanism that allows to add
>> new styles in the stable 2.1 series in a backward compatible way. See
>> lib/Development.lyx for details.
>
> Ah, I didn
Richard Heck wrote:
> So let me just be clear: As things presently are, viz:
>
> #define LYX_FORMAT_LYX 474 // rgh: dummy format change for Chunk switch
> #define LYX_FORMAT_TEX2LYX 473
>
> what tex2lyx will do is produce a file with version 473. LyX will then
> attempt to read this file, and in
Richard Heck wrote:
> On 05/27/2013 10:03 PM, Hashini Senaratne wrote:
>> Hello all,
>>
>> I am glad to hear that my proposal "Horizontal scrollbar for tables and
>> math for LyX" submitted has been accepted for Google Summer of Code 2013.
>> Thank you (all the developers and specially my two ment
Uwe Stöhr wrote:
> The question is where we should draw the cutting line. After the release
> of LyX 2.1 it will not be possible to add styles to layout files until LyX
> 2.2 in perhaps 2 years.
This is not true anymore. I implemented a mechanism that allows to add new
styles in the stable 2.1 s
Richard Heck wrote:
> I must have missed this rule. In any event, I've never followed it. I
> don't know how tex2lyx works, and I don't propose to learn just so I can
> do other format changes.
This is documented in lib/doc/Development.lyx. Updating tex2lyx at the same
time as LyX is not a must,
Pavel Sanda wrote:
> Hi (Georg),
>
> for a decade these files are not used and I don't suppose they will be
> used ever, cf. da92b37c1dac93. So they should go. Scream now or never.
Fine with me.
Georg
Stephan Witt wrote:
> When trying to make a dist tar-ball I get this:
>
> make[2]: *** No rule to make target `test/DummyDocument.lyx.lyx', needed
> by `distdir'. Stop. make[1]: *** [distdir] Error 1
> make: *** [distdir] Error 1
This is because tex2lyx does not output the correct files for inc
Vincent van Ravesteijn wrote:
> Development of new features and/or fixes that can wait for LyX 2.1.x, or
> 2.2.0, can take place in the new features repository.
IMHO it would be very good to concentrate on 2.1.0 and not to work on 2.2 or
2.1.x stuff at all until 2.1.0 is released. Otherwise it w
Julien Rioux wrote:
> On 08/04/2013 3:20 PM, Georg Baum wrote:
>> If nobody beats me to it I'll have a look, but since I am very short on
>> time currently this may only be in about two weeks.
>>
>>
>> Georg
>>
>>
>
> Ping!
Sorry, I forgot
Liviu Andronic wrote:
> I updated the patch to reflect this. Is it OK for inclusion in trunk?
>
> I also updated the templates, EPS-cropped.lyx and PDF-cropped.lyx, to
> include some minimal documentation on their intended use.
This one looks good!
Georg
Vincent van Ravesteijn wrote:
> The branch, master, has been updated.
>
> - Log -
>
> commit 6f16814d3b9f51907cadfb97282d95ee769cb6fe
> Author: Vincent van Ravesteijn
> Date: Tue May 14 18:41:33 2013 +0200
>
> Fix check_layo
Pavel Sanda wrote:
> Forget about it: Trac is innocent, @lyx.org eats those mails for spam
> reasons. Lelearning classifier with false positives from last days put
> things back into order.
Indeed, I discovered the missing messages in the spam folder as well. How
did you relearn? I just deleted
Kornel Benko wrote:
> Am Montag, 13. Mai 2013 um 21:56:33, schrieb Georg Baum
>> Kornel, it would be nice if you could do the cmake part.
>>
>
> Sure, but at least this one part
> -Wl,--allow-multiple-definition
> does not look portable.
No, it is not portab
Liviu Andronic wrote:
> Dear all,
> I've just updated a patch that simply adds two new converters to LyX:
> pdflatex -> pdfcrop and DVI -> EPS. They're also accompanied by two
> templates, which only set 'empty' page style and predefine the default
> output format.
>
> This basically allow us to
Vincent van Ravesteijn wrote:
> On Sunday, May 12, 2013, Pavel Sanda wrote:
>> Vincent van Ravesteijn wrote:
>>> I got them all.
>>
>> ldm conspiracy :))
>>
>
> We really thought you received everything, because you agreed on
> everything that we decided.
Seriously: It would be good to fix
Abdelrazak Younes wrote:
> I think it is worth investing time in it. At the meeting everybody
> agreed that we should have one build system in the long run. But to make
> cmake official we need to achieve the following:
> 1) implement the missing feature of autotools in cmake, especially for
> MAC
Liviu Andronic wrote:
> Dear all,
> In trunk we have two EPS formats:
> \Format epseps EPS"" "%%"""
> "vector""image/x-eps"
> \Format eps2 eps"EPS (uncropped)" "" "%%" ""
> "vector"""
>
> What is eps2 for? What is the diff
Pavel Sanda wrote:
> Liviu Andronic wrote:
>> On Sun, May 12, 2013 at 7:52 PM, Pavel Sanda wrote:
>> > Seems I'm no more getting mails when bugs are changed in trac.
>> > Anyone else?
>> >
>> I'm getting mines.
>
> Indeed it seems if CC myself with lyx unrelated email it works, if I'm
> CC-ed ei
Richard Heck wrote:
> No, I just meant that we would have to include it in our sources, since
> we cannot rely upon libxml to be available on actual machines that are
> running non-Linux OSs. It's available for that OS, yes, but it's not
> actually going to be installed. Unlike on Linux, where it
Vincent van Ravesteijn wrote:
>> Thanks Vincent, I no longer get a crash. I still have the following
>> issues (let me know if I should open up tickets):
>
> I'm not too enthusiastic about opening tickets just because code has
> been committed which hasn't been tested beforehand.
It has been tes
Richard Heck wrote:
> There are a couple issues here. One is the problem of branches.
> Previously, we'd have "pasted" the copied paragraphs into the temporary
> Buffer, and with it whatever branch insets were in the copied material,
> not paying any attention at all to whether those branches exis
Cyrille Artho wrote:
> Hi Georg,
> I'm not familiar enough with the capabilities of LaTeX macros to be the
> final judge on that, but it seems plausible that macros may work better
> for many features.
>
> However, it is also desirable to keep the LaTeX code simple. For features
> that are merely
Scott Kostyshak wrote:
> I'm getting a SIGSEGV now. I can reproduce on Ubuntu 12.04 with the
> following: 1. Open the User's Guide, Additional Features, Embedded
> Objects, or Math manual. 2. Select all
> 3. Copy
Thanks, I can reproduce it. The attached patch works around the problem. It
looks l
Cyrille Artho wrote:
> I think it is possible to save some internal features of LyX (inset
> collapsed/expanded, notes, etc.) in LaTeX as well. They could be exported
> as special LaTeX comments. Of course, editing these comments would lose
> the extra data, but we'd have to trust people working o
Liviu Andronic wrote:
> Dear Daniel,
>
>
> On Sun, Apr 14, 2013 at 10:26 AM, Daniel Vainsencher
> wrote:
>> Please CC me on answers.
>>
>> I often collaborate with people who (still) prefer LaTeX, and also submit
>> papers to conferences that make it easy to submit latex via
>> style/class/samp
Jean-Marc Lasgouttes wrote:
> OK, let's stay with the submenu. Would it make sense to change all the
> entries using LFUN_PASTE to by OptItems and to be grouped together at
> the start of the menu? This way thing would look more like
> autodetection. Frankly having a LinkBack entry on Linux wherea
Jean-Marc Lasgouttes wrote:
> Le 08/04/13 21:27, Georg Baum a écrit :
>> Nico Williams wrote:
>>
>>> Can you give the user the option to paste [as] LaTeX?
>>
>> This would be easy to implement, but we have already many paste options,
>> I'd on
Georg Baum wrote:
> 3.2.1 is available in debian squeeze (the current stable version).
Wrong, it is 3.1.3, but does not matter.
Georg
Pavel Sanda wrote:
> Stephan Witt wrote:
>> > What's the status of python 3 on fedora/debian/suse?
>>
>> On my Mac (latest version Mac OS X 10.8.3) the default is 2.7.2.
>
> Default is not so important, important is 3.x availability, we have
> mostly working selection mechanism thanks to Enrico.
Pavel Sanda wrote:
> Tommaso Cucinotta wrote:
>> Yes, but the problem is that the ::findFile() machinery is called twice
>
> Which is a mistake, we used to call it only once. Unfortuntaly both
> me and Georg is short of time so it will perhaps take some time to address
> all the mess which seem t
Pavel Sanda wrote:
> Guenter Milde wrote:
>> Where do I have to apply.
>
> Pretty much by screaming here.
>
> The usual prerequisity is that you stay around for some time
> while providing patches, willingness to fix problems
> caused by your commits and at least in the beginning
> asking for ac
Nico Williams wrote:
> Please, please give me an option to have LyX do nothing regarding git.
> In particular I want an option to have LyX make absolutely no
> commands like: git add, git commit, git pull, git push, git merge, git
> cherry-pick, git branch, or git checkout, and no versions of any
Pavel Sanda wrote:
> Georg Baum wrote:
>> > Perhaps we can drop this check-out behaviour if it makes troubles, wait
>> > for Georg's opinion. There is also still the problem that we run
>> > GIT::find_file 2x IIRC.
>>
>> Really? I thought I go
Nico Williams wrote:
> Can you give the user the option to paste [as] LaTeX?
This would be easy to implement, but we have already many paste options, I'd
only do it if there was a strong opinion about it.
>> 3) You notice (a very small) delay if tex2lyx is run, but I believe that
>> this is mai
Jean-Marc Lasgouttes wrote:
> 02/04/2013 21:19, Georg Baum:
>> This is a patch that was rotting in trac for ages, and I don't want it to
>> miss another major release. It improves both copying to and pasting from
>> the system clipboard.
>
>> Can this
Rudi Gaelzer wrote:
> It seems that I have to amend what I assumed earlier.
> It looks like that the problem is really with the master/child structure.
> Take a look at the files attached. The master is newfile1.lyx and the
> child is child.lyx (surprise!)
> The same xfig figure is rendered at th
Tommaso Cucinotta wrote:
> Hi,
>
> I just noticed that GIT::findFile() doesn't seem to work, namely if I open
> with git any file within the lyx sources tree, it always asks me whether I
> want to retrieve the file from the VCS (which in turn causes all test
> cases in autotests to fail, but it's
Pavel Sanda wrote:
> The problem is that such behaviour is intentional i guess, my
> understanding is File exists & is in repo -> we load with git support
> File exists & not in repo-> ?? porcelain case, we don't load with VCS
> support File !exists& we are in repo (more exactly within dir structu
Guenter Milde wrote:
> On 2013-03-31, Georg Baum wrote:
>> Guenter Milde wrote:
>>> On 2013-03-27, Georg Baum wrote:
>
> ...
>
>>> Without file inclusions, the "LaTeX encoding" of the exported file does
>>> not matter for the Postscript/PD
Scott Kostyshak wrote:
> Can this go in?
Of course! It is pretty clear that these paths are not absolute on purpose,
and how the correct fix looks like. IMHO you don't need to post such obvious
fixes to the list.
Georg
This is a patch that was rotting in trac for ages, and I don't want it to
miss another major release. It improves both copying to and pasting from the
system clipboard.
paste: In addition to plain text and LyX format, both HTML and LaTeX are
recognized on the clipboard. Since I did not find any
Guenter Milde wrote:
> On 2013-03-27, Georg Baum wrote:
>> Guenter Milde wrote:
>>> This is why I propose:
>>> * document the issue (for all included files!)
>>> * use the "locale encoding" for LaTeX export.
>
>> What do you mean by "l
Helge Hafting wrote:
> On 29. mars 2013 13:38, Kornel Benko wrote:
>> I seem unable to find strings using non ascii chars (e.g. latin2)
>>
>> (Please try to use UTF-8 encoding to read this mail)
>>
>> The regex search string may be "pou.i.", so I was expecting to find
>>
>> e.g. "použiť". I have t
Richard Heck wrote:
> On 03/15/2013 04:44 PM, Georg Baum wrote:
>> Some time ago we had a discussion about what changes to layout files are
>> allowed in a stable release. There were several proposals, from simple
>> but limited to powerful but complicated. Meanwhile I had
As you probably all know, features which are not covered by regularly
executed tests will break over time. Therefore I created a test for the new
Layout::write() functionality (see attached). It works, and it already found
a couple of bugs in my first implementation. However, there are several
Guenter Milde wrote:
> On 2013-03-26, Scott Kostyshak wrote:
>> On Tue, Mar 26, 2013 at 6:57 AM, Jean-Marc Lasgouttes
>> wrote:
>>> 26/03/2013 11:54, Guenter Milde:
>
> Can we use iconv to convert the verbatiminput file to the correct
> encoding when we copy it to the temporary directory?
Richard Heck wrote:
> I wouldn't object to enabling it by default in 2.1. If people felt we
> shouldn't
> change how existing installs work, then it would be trivial to add
> something to prefs2prefs to set it as off for people who are upgrading
> from 2.0. Seems quite sensible, really.
IMHO this
Scott Kostyshak wrote:
> Thanks for the explanation. If I understand correctly then,
> DocumentTexteBidon.txt should have latin9 encoding when compiling with
> latex/pdflatex and should have utf8 encoding when compiling with
> xetex/luatex and thus it is impossible to have both (unless we have
> t
Scott Kostyshak wrote:
> Without this, I get UTF-8 errors. ps2pdf and pdflatex compile fine but
> LuaTeX does not like the current Latin-1 encoding of
> DocumentTexteBidon.txt.
>
> Is this the right fix?
Unfortunately not. This is a LaTeX limitation: files included via
\verbatiminput need to be
Kornel Benko wrote:
> Am Samstag, 23. März 2013 um 10:21:50, schrieb Kornel Benko
>
>>
>> This setting comes from
>> Tools->Preferences...->File Handling->Converters->
>> Converter File Cache-> (Enabled)
>> Maximum Age (in days)-> (170)
>>
Jean-Marc Lasgouttes wrote:
> What if the new textclass is modified in 2.1.(x+1) ? Does it get updated
> in the document? IOW, should these layout files have a version of their
> own to tell which one is the latest and greatest?
Good question, I did not think about that yet. We could either use
Jürgen Spitzmüller wrote:
> So I inverstigated further and came up with the attached, which I
> think pinpoints the real issue (a missing toolbar initialization) and
> fixes the remaining problems for me.
Thanks for your work! BTW I am not surprised about the side effects, I found
the session co
Jean-Marc Lasgouttes wrote:
> So, do we want that in the code?
Yes please! As you showed, it is already useful, and even if it is
inaccurate, somebody else might have an idea how to improve it.
Georg
Jürgen Spitzmüller wrote:
> 2013/3/19 José Matos:
>> Actually my minor quibble here is the unwanted appearance of the IPA
>> toolbars any time I start lyx
>
> Yeah, they are a real PITA.
This is caused by reading/writing the session info at the wrong time. I did
some analysis of the problem at
Richard Heck wrote:
> On 03/17/2013 01:05 PM, Jürgen Spitzmüller wrote:
>> Due to the existence of an OpenDocument > PDF converter (unoconv -f pdf
>> -- stdout $$i > $$o), the ps2pdf route fails for me in trunk. LyX tries
>> to go the route via odt instead of the preferred latex > dvi > ps > pdf
>
Juergen Spitzmueller wrote:
> This should be tested with as much beamer documents as possible (I
> have already done so), also, tex2lyx now probably produces invalid LyX
> files.
Why should tex2lyx produce invalid files? It will probably produce lots of
ERT for beamer documents produ
Some time ago we had a discussion about what changes to layout files are
allowed in a stable release. There were several proposals, from simple but
limited to powerful but complicated. Meanwhile I had another idea which is
IMHO quite simple but still powerful: Introduce a new "force local" flag
Kornel Benko wrote:
> Not forgotten, I didn't touch them intentionally.
> Since they are input files they are not a subject to compare.
> But, of course, it is better to have them in a new format.
They are no input files, but tex2lyx does not apply the -roundtrip stuff to
included files currentl
Jürgen Spitzmüller wrote:
> Kornel Benko wrote:
>>
>> This grid is a good idea, I also thought about it. Since I am
>> no-qt-expert, I did not dig farther.
>
> I've implemented something along this line.
Very nice!
Georg
Kornel Benko wrote:
> So, now the bisects ends (with help from Scott BTW). And after some
> computer crashes. (Hopefully removing plenty of dust helps!)
>
> Bisect leads to:
> cd17d87e47d522c3c848a49ac63602a0a8a1b635 is the first bad commit
> commit cd17d87e47d522c3c848a49ac63602a0a8a1b635
> Auth
Jean-Marc Lasgouttes wrote:
> Le 26/02/2013 22:23, Georg Baum a écrit :
>> Jean-Marc,
>>
>> many thanks for your noweb improvements! While investigating how your
>> test document could be added to the test suite I stumbled over some
>> encoding warnings that ar
Kornel Benko wrote:
> I have a solution for this.
>
> 1.) In lib/layouts/stdfloats.inc rename
> Type algorithm
> to
> Type algorithmfloat
> 2.) Increment lyx-format, becase now lyx-file changes entries
> from
> \begin_inset Float algorithm
> to
> \begin_inset Flo
Scott Kostyshak wrote:
> Is it possible that this broke export of examples/achemso.lyx to
> LyXHTML? When I try to export it to LyXHTML, it is as if it's in an
> infinite loop or that it's waiting on something.
>
> git bisect led be here, but git bisect has led me astray before (due
> to my own m
Jean-Marc,
many thanks for your noweb improvements! While investigating how your test
document could be added to the test suite I stumbled over some encoding
warnings that are currently output for CJK.tex. I added this warning (in
iparserdocstream::setEncoding()), but when looking at the actual
Kornel Benko wrote:
> Am Dienstag, 26. Februar 2013 um 09:23:47, schrieb Richard Heck
>
>>
>> I'm not that familiar with the new framework for dealing with these
>> packages, but a question about this:
Youd do not need to chnage more (in the LyX cpp code) to add a new package.
However, the cur
Jean-Marc Lasgouttes wrote:
> Le 24/02/2013 19:06, Georg Baum a écrit :
>> This error reminds us that the current structure of parse_text() is
>> reaching its limits. It also has a performance problem, so some
>> refactoring is needed, but IMHO not for 2.1.
>
> On w
Georg Baum wrote:
> Fix lyx2lyx for layout files with umlauts
>
> lyx2lyx died with UnicodeDecodeError: 'ascii' codec can't decode byte
> if a layout with a non-ASCII character in the file name was used,
> since the textclass member of the LyX
Guenter Milde wrote:
> On 2013-02-17, Georg Baum wrote:
>
>> This is not needed: the simple force flag does not force for any utf8
>> encoding. It worked always like that, but now I added an explanation to
>> the unicodesymbols file.
>
> The "force"
Pavel Sanda wrote:
> Richard Heck wrote:
>> On 02/18/2013 02:17 AM, Pavel Sanda wrote:
>>> Uwe Stöhr wrote:
Pavel, would you again like to take care as release maintainer?
>>> My private thought is that releasing 2.1 before meeting will hurt its
>>> stability due to the time left.
>>
>> I wou
Jean-Marc Lasgouttes wrote:
> Le 15/02/2013 19:03, Kornel Benko a écrit :
>> Thanks Jean-Mark. But a new error raised: import of CJKutf8.tex
>>
>> goes wrong.
>>
>> This file is really short. The string "hello" should not be lost IMHO.
>
> The ugly bug with verbatim environment is now fixed. The
Kornel Benko wrote:
> It is not needed for utf8, but maybe it would be handy for other
> encodings. Therefore the generalized syntax "force!=..." may well be
> helpful.
Sure. But I am personally too lazy to implement it without any existing use
case.
Georg
Scott Kostyshak wrote:
> Looks good. Thanks for adding this. I will add stuff eventually, but
> I'm not sure when. I'm also not sure what the relationship should be
> between this doc and the README files in '/development/autotests'.
> Perhaps the README files should be for technical information,
Guenter Milde wrote:
> Dear LyX developers,
>
> the "unicodesymbols" file contains many replacements that require the
> "textcomp" package. Some are "forced", others not, e.g.
>
> 0x00a9 "\\textcopyright" "textcomp" "" # COPYRIGHT SIGN
>
> 0x00ac "\\textlnot" "textcom
Scott Kostyshak wrote:
> It's not possible to just use the same application that was used in
> previous years?
It is a process, not a static result.
>> Not at the moment. Unless somebody complains I'll simply create this
>> document when I'll find some time again, and if you'd like a specific
>>
Jean-Marc Lasgouttes wrote:
> Le 15/02/2013 19:03, Kornel Benko a écrit :
>
>> Thanks Jean-Mark. But a new error raised: import of CJKutf8.tex
>
> OK, I failed to test properly... Shall I revert? I do not know when I
> will have time to test/fix.
This is fixed by Uwes workaround for bug 8525 as
Pavel Sanda wrote:
> Pavel Sanda wrote:
>> -doVCCommand("git log -n 1 --pretty=format:%H . > " +
>> quoteName(tmpf.toFilesystemEncoding()),
>> +doVCCommand("git describe --long > " +
>> quoteName(tmpf.toFilesystemEncoding()),
>
> maybe adding dirty flag makes sense as well: git describe -
Scott Kostyshak wrote:
> On Wed, Feb 6, 2013 at 3:05 PM, Georg Baum
> wrote:
>>
>> This has been requested several times, but I did not find the time to
>> write one up to now. I do not want to dump it into a hidden place where
>> nobody will find it. Recently I
Pavel Sanda wrote:
> Georg Baum wrote:
>> commit 22b7ad2b0a6c228f234bcf7f5a0b164fca17e122
>> Author: Georg Baum
>> Date: Thu Feb 7 22:07:22 2013 +0100
>>
>> Implement revision info for git
>>
>> +bool GIT::getTreeRevisionInfo()
>> +{
&
Pavel Sanda wrote:
> I see more scanMasters added findFile. That means we ask findFile to check
> whether we are under VCS and if yes we create new VCS object which call
> scanMaster in contructor which in turn call findFile again. Is this
> duplicity needed?
This is needed for detecting the UNVE
Scott Kostyshak wrote:
> Thanks for the explanation. Should I make a trac enhancement request for
> this?
Yes please.
Georg
Jean-Marc Lasgouttes wrote:
> Le 06/02/2013 13:43, Kornel Benko a écrit :
>> tex2lyx tests:
>> 1.) Remove empty layout 'Plain'
>> 2.) Adapt to changed look of layout 'Verbatim'
>
> I am not sure (yet) whether this is a good thing. The fact is that my
> new code avoids extra empty p
Scott Kostyshak wrote:
> Ah, I had a user directory from a previous version that it was using.
>
> I then emptied the directory and ran make check. I got a lot of errors
> and assertions. I then started LyX so that it would configure. Then I
> exited and ran make check and everything went well.
>
Guenter Milde wrote:
> Actually, both dotless j and Angstrom sign are not defined in any of
> inputenc's encoding definition files, so IMO the simple "force" is OK.
>
> On the other hand, as no other encoding table contains these symbols, LyX
> will write the "unicodesymbols" replacement in any n
Uwe Stöhr wrote:
> I know this, but why are you against checking for the wasy fonts.
I am not against checking the font. The current version of the check is
fine, but I replied to the commit message of a different one.
Georg
Pavel Sanda wrote:
> I'm not sure about poor man solution for RCS rename. If we let history ,v
> on place it will be forgotten by the user, if we delete it user can be
> surprised that he lost the whole history after rename. I wonder if
> unimplemented RCS rename wouldn't be better in the end?
I
Uwe Stöhr wrote:
> The branch, master, has been updated.
>
> - Log -
>
> commit 3cba8fa9be09cefdbb145415fe6132383d27aa88
> Author: Uwe Stöhr
> Date: Wed Jan 23 22:01:06 2013 +0100
>
> chkconfig.ltx: check for wasy
>
>
Scott Kostyshak wrote:
> On Mon, Jan 21, 2013 at 3:54 AM, Jürgen Spitzmüller wrote:
>>
>> Not for the first one. The second one is because cancel is loaded with an
>> option manually in the preamble, but has already been automatically
>> loaded by LyX without options before.
It is even worse: ca
The attached patch implements two new VCS commands which I already announced
some months ago. Only svn supports them fully, but I implemented a poor mans
version for CVS and RCS. These commands are useful i several cases, e.g. if
you give a lecture that is evolving each year, and want to keep yo
Scott Kostyshak wrote:
> On Sun, Jan 20, 2013 at 11:42 AM, Enrico Forestieri
> wrote:
>> The branch, master, has been updated.
>>
>> - Log -
>>
>> commit 1d5eec8744e0f000d582945aec50ba503149f313
>> Author: Enrico Forestieri
>> Date:
1201 - 1300 of 6177 matches
Mail list logo
