Re: \input@path - two slashes, quotation marks
PhilipPirrip wrote:
> I suspect the other slash was added as a bug fix for those OS's that do
> not have it at the end of the path, can't see any other reason.
> So I suppose this should be tested on OSX and Windows as well.
It is not an OS issue. LyX has an OS abstraction layer for this kind of
stuff, and therefore the code that determines the path returns a slash at
the end for all OSes.
I'll remove the second slash (not in the stable 2.1 branch of course), and
we'll see if anybody screams (but I doubt that).
> I wish this was true, but no... \filename@parse only *parses* (no search
> involved) its argument for the three parts, and it does it in a very
> primitive way.
>
>
> \documentclass{article}
> \begin{document}
> \makeatletter
> \filename@parse{/home/user/doesn.t exist/test v2.1 new.bib}
> \texttt{\meaning\filename@area}
>
> \texttt{\meaning\filename@base}
>
> \texttt{\meaning\filename@ext}
>
> \texttt{\meaning\input@path}
> \makeatother
> \end{document}
>
>
> check:
> http://tex.stackexchange.com/questions/39634/how-to-trim-tex-for-each-filename-read-from-an-external-file
OK, then I misunderstood the TeX code (I used to be better at that).
> Since the way \input@path is being used in the biblatex hack from
> http://wiki.lyx.org/BibTeX/Biblatex is barely legal, maybe LyX should
> define its own command, say \LyX@basepath that'd contain the absolute
> path to the master .lyx document (no qoutes, no curly braces - only for
> the brave).
> Would you be willing to do that? (being that biblatex support is nowhere
> on the horizon yet)
After all these discussions it is clear that something like this is needed.
However, I do not want to clutter all documents with that (since 95% of the
users don't need it). I would prefer a solution where we extend the layout
definition language so that you could use a placeholder that will be
replaced by LyX with the master document path. Then everybody who needs this
path could write a module that pulls in the path into a LaTeX macro in the
most simple case, or in more advanced cases it could directly be used in the
preamble code that needs it.
Georg
Re: -std=c++11 and [PATCH] Improve the display of the source (bugs #6501,#7359)
Jean-Marc Lasgouttes wrote: > Le 27/08/2015 22:00, Georg Baum a écrit : >> We can at least turn c++11 on automatically for "non-weird" compilers >> (and I think we should do it). > > The following patch (on top of the previous one) does this. OK? Yes, this looks good. Georg
Re: [PATCH] Re: -std=c++11 and [PATCH] Improve the display of the source (bugs #6501,#7359)
Jean-Marc Lasgouttes wrote: > Le 27/08/2015 22:00, Georg Baum a écrit : One problem that we have is that the compiler has to be in c++11 mode _and_ the configure script has to be aware of it. Currently weird compilers are not handled at all. >> >> We can at least turn c++11 on automatically for "non-weird" compilers >> (and I think we should do it). > > It occurred to me that it is possible to detect C++11 even with gcc > 4.[3-6] using whatever is defined by the compiler. > > Georg, does this make sense to you? Also I use c++11 mode instead of > gnu++11; we do not need any extension. Yes, the automatic detection by preprocessor macros is the best method IMHO. However, since we do not know whether we'll need to modify the #ifdef for other compilers again, could we not have this in config.h.in #if __cplusplus >= 201103L || defined(__GXX_EXPERIMENTAL_CXX0X__) #define LYX_USE_CXX11 #endif and then keeping everything in src/ unchanged? That looks even cleaner to me. Georg
Re: Regression in lyx2lyx box alignment
On Sun, Jun 21, 2015 at 5:46 PM, Scott Kostyshak wrote: > On Sun, Jun 21, 2015 at 10:41:27PM +0200, Uwe Stöhr wrote: >> Am 20.06.2015 um 05:11 schrieb Scott Kostyshak: >> >The attached file produces a left-aligned box in 2.1.3 but a centered >> >box for 2.2dev. >> > >> >Uwe I remember you've done a lot of work on boxes in master. Can you >> >take a look? >> >> Hi Scott, >> >> I am currently abroad and can therefore not have a look the next day. > > No problem. Thanks for letting me know! > > Enjoy your time abroad. Hi Uwe, I get the feeling you are still busy, but I wanted to bump this email in case you had time to take a look. We still haven't made concrete plans for 2.2.0 so there should still be some time before it is released. Scott
