http://www.lyx.org/trac/changeset/28141 fixes http://bugzilla.lyx.org/show_bug.cgi?id=5686. Now "\"
characters in the url field are translated in the background to "/". So one can insert path to files
as you like - Windows or Unix style.
The result, e.g.
file:C:/file.txt
is handled correctly by
> Jürgen Spitzmüller wrote:
>> > AFAIK, it is only usable in math. So we might want to _add_ it only
>> > in this case (if we ever need it).
>
> Would be the attached. Some testing would be nice.
The patch is OK from my point of view and after testing.
> BTW, why did we remove the %-items from h
Jean-Marc Lasgouttes wrote:
> Pavel Sanda writes:
> > Manveru schreef:
> >> I hadn't read this in manual, but from your explanations it seem to be
> >> very user not-friendly feature. It is not natural to users entering
> >> new name in that field every time they want new group. Without reading
>
Pavel Sanda wrote:
Richard Heck wrote:
My worry was: what if the path doesn't exist?
i know, but the current patchchanger interface doesn't provide that info.
i have tried filename.getcwd() but that failed for links.
Can we check if the path exists and can be cd'd t
sa...@lyx.org wrote:
> Author: sanda
> Date: Tue Jan 13 22:33:56 2009
> New Revision: 28138
>
> URL: http://www.lyx.org/trac/changeset/28138
> Log:
> Add LFUN_VC_COMMAND.
> http://www.mail-archive.com/lyx-devel@lists.lyx.org/msg147331.html
i would like to have this in branch. Juergen?
pavel
Richard Heck wrote:
>>> My worry was: what if the path doesn't exist?
>>>
>>
>> i know, but the current patchchanger interface doesn't provide that info.
>> i have tried filename.getcwd() but that failed for links.
>>
>>
> Can we check if the path exists and can be cd'd to beforehand?
ok,
Pavel Sanda wrote:
Richard Heck wrote:
Is some kind of error checking needed here?
i will look.
My worry was: what if the path doesn't exist?
i know, but the current patchchanger interface doesn't provide that info.
i have tried filename.getcwd() but that fai
Bernd Sellentin wrote:
Hi,
since lyx 1.6 ERT does some strange and unwanted insertion like
\foreignlanguage{ngerman} and {} when I modify an existing ERT. You can see
this if you open VIEW->Source.
Mostly this ERT-modified code does not compile anymore.
I found 2 workarounds:
- save-close-reop
Richard Heck wrote:
>>> Is some kind of error checking needed here?
>>>
>>
>> i will look.
>>
>>
> My worry was: what if the path doesn't exist?
i know, but the current patchchanger interface doesn't provide that info.
i have tried filename.getcwd() but that failed for links.
pavel
Jürgen Spitzmüller wrote:
rgheck wrote:
URL: http://www.lyx.org/trac/changeset/28128
Log:
Improve the rendering of BibTeX data in InsetCitation. This backports a
handful of commits from trunk.
Status.16x, please.
Sorry. Will I ever learn?
rh
Jürgen Spitzmüller writes:
> I see your points. I'm pondering all this as well, and I'm still
> undecided (apart from the fact that I do not like renaming of
> "Labeling").
I have to say that, personnally, 'Labeling' does not sound like a list
to me. But List is of course too vague. Would there
Pavel Sanda wrote:
Richard Heck wrote:
It seems potentially confusing to use $$i for two different things, and I
can imagine wanting the path in the latter case. I think there's some
precedent here, no?
i'm aware of $$i (input), $$o (output) and $$s (system) in converters commands
and
Guenter Milde wrote:
>> As already said, I'm opposed to changing the name of Labeling. Labeling
>> is a well established concept in the KOMA classes, and it is known and
>> documented under this name. List, on the other hand, is just our own
>> invention. "Actually, this is called Labeling, but we
On 2009-01-13, Jürgen Spitzmüller wrote in gmane.editors.lyx.devel:
> Guenter Milde wrote:
... use one common name for list/labeling in both KOMA and non-KOMA
documents.
>> Rationale:
>> 1. Two names for one object in one application are just confusing.
>> 2. In LaTeX, list is a gener
hi,
make check now fails for lyx-1.6.
test_convert now returns
1.1001 instead of 1.1 for convert(1.1)
what should be the correct return?
pavel
On Tuesday 13 January 2009 02:43:36 John Weiss wrote:
> On Sat, Jan 10, 2009 at 07:06:41PM +0100, Pavel Sanda wrote:
> > Angus Leeming wrote:
> > > We had one curmudgeonly gentleman, John Weiss, who point blank refused
> > > to licence his contribution to LyX under the GPL version 2 or later.
> > >
Christian Ridderström wrote:
> Is the size a problem?
for me no.
> If so, what can I do to avoid it?
in svnmailer.conf i see for_repos and for_paths variables.
pavel
Hi,
When comitting changes to web pages, the attached 'patches' are
unfortunately rather big. I see that the automatically generated posts are
in the order of 40k to 80k sometimes.
Is the size a problem?
If so, what can I do to avoid it?
/Christian
--
Christian Ridderström, +46-8-768 39 44
John Weiss wrote:
> The upshot is: you cannot put a GPL'd file into a codebase under the
> Artistic License without changing the license of the entire codebase
> to GPL. You can, however, put an Artistic License into a GPL'd
> codebase with no effect on the other files in the codebase (which
> re
Guenter Milde wrote:
> In the documentation list, there came a question about documenting the
> Lyx-List, while the actual Style is called Labeling (the Guide uses KOMA
> script).
>
> In my view, instead of documenting that a LyX-List is called Labeling in
> some document classes, ...
>
>>> "The
rgheck wrote:
> URL: http://www.lyx.org/trac/changeset/28128
> Log:
> Improve the rendering of BibTeX data in InsetCitation. This backports a
> handful of commits from trunk.
Status.16x, please.
Jürgen
21 matches
Mail list logo
