FWIW, I've done some LyX->LyXHTML->XML conversions, as well as
LyX->XML via Python (to fix text styling open/close mismatching) and
then XSLT.
You can find that work here: https://github.com/nicowilliams/lyx2rfc
It's a bit old and rotted, but it illustrates something like
LaTeX->XML, but for LyX
On Tue, Feb 17, 2015 at 08:45:04PM +0100, Georg Baum wrote:
One option which is probably easy to implement would be to mark the start
and end of the ERT inset with two unicode symbols from the private use area
(similar to META_INSET): We could define
char_type const MATH_ERT_BEG =
On Tue, Feb 17, 2015 at 08:45:04PM +0100, Georg Baum wrote:
> One option which is probably easy to implement would be to mark the start
> and end of the ERT inset with two unicode symbols from the private use area
> (similar to META_INSET): We could define
>
> char_type const MATH_ERT_BEG =
On Mon, Apr 7, 2014 at 8:24 AM, stefano franchi
stefano.fran...@gmail.com wrote:
I haven't done any concrete coding in the area, but my favorite strategy
for the Word--LyX step would tend to lean toward a direct parsing of the
XML format produced either by Word (the docx format) or by
On Mon, Apr 7, 2014 at 8:24 AM, stefano franchi
wrote:
> I haven't done any concrete coding in the area, but my favorite strategy
> for the Word-->LyX step would tend to lean toward a direct parsing of the
> XML format produced either by Word (the docx format) or by
>
On Fri, Nov 8, 2013 at 2:48 AM, Vincent van Ravesteijn v...@lyx.org wrote:
On Thu, Nov 7, 2013 at 10:40 PM, Nico Williams n...@cryptonector.com
wrote:
_Never_ push -f to any repo that *others* (or even you, in other
workspaces) pull from.
In general it is better to not rewrite history
On Fri, Nov 8, 2013 at 2:48 AM, Vincent van Ravesteijn <v...@lyx.org> wrote:
> On Thu, Nov 7, 2013 at 10:40 PM, Nico Williams <n...@cryptonector.com>
> wrote:
>> _Never_ push -f to any repo that *others* (or even you, in other
>> workspaces) pull from.
>
> In
On Thu, Nov 07, 2013 at 09:23:15PM +, Tommaso Cucinotta wrote:
Sure, feel free to commit them. Guess that in multi-user commit mode,
it's much better to NOT rewrite history, so we won't use push -f, right ?
(Vincent ?).
_Never_ push -f to any repo that *others* (or even you, in other
On Thu, Nov 07, 2013 at 09:23:15PM +, Tommaso Cucinotta wrote:
> Sure, feel free to commit them. Guess that in multi-user commit mode,
> it's much better to NOT rewrite history, so we won't use push -f, right ?
> (Vincent ?).
_Never_ push -f to any repo that *others* (or even you, in other
Hi, this is pretty awesome indeed!
Would it be possible to do somethin OTR-like (in the sense of hiding
extra data) for exchanging cursor movement operations / cursor
location, and changes (typing, ...)? That would make it possible to
collaboratively edit LyX docs.
Hi, this is pretty awesome indeed!
Would it be possible to do somethin OTR-like (in the sense of hiding
extra data) for exchanging cursor movement operations / cursor
location, and changes (typing, ...)? That would make it possible to
collaboratively edit LyX docs.
On Thu, Oct 17, 2013 at 1:49 PM, Pavel Sanda sa...@lyx.org wrote:
Josh Hieronymus wrote:
1. Breaking an XHTML file into smaller files can lead to better performance
I think that for people who use XHTML as export format for different formats
won't be happy about this.
Indeed, I would be
On Wed, Oct 16, 2013 at 5:23 PM, John Tapsell johnf...@gmail.com wrote:
Like it says, that commit is a merge..
You can just checkout that commit: git checkout HEAD@{27}
or reset to that commit: git reset HEAD@{27}
Personally I advise against using git reset except when you *really*
know
In general, if you stay away from destructive operations, git is quite
safe. If you find yourself wanting to perform a destructive
operation, make sure first that any extant changes in your workspace
are committed so that you can always get them back from the reflog.
Committing stuff you don't
On Thu, Oct 17, 2013 at 8:11 PM, Cyrille Artho c.ar...@aist.go.jp wrote:
I once made a mistake with git, too, that took a while to recover.
IMHO git works well if
(1) You are very careful and RTFM closely before using reset, rebase.
Rebase is not destructive: your commits remain available
On Thu, Oct 17, 2013 at 8:02 PM, Vincent van Ravesteijn v...@lyx.org wrote:
Nico Williams schreef op 18-10-2013 0:59:
The ironic thing using Git is that it is very safe if and only if you know
your way around with Git. I remember that when I started using Git, I
frequently lost stuff
On Thu, Oct 17, 2013 at 1:49 PM, Pavel Sanda wrote:
> Josh Hieronymus wrote:
>> 1. Breaking an XHTML file into smaller files can lead to better performance
>
> I think that for people who use XHTML as export format for different formats
> won't be happy about this.
Indeed, I would
On Wed, Oct 16, 2013 at 5:23 PM, John Tapsell wrote:
> Like it says, that commit is a merge..
>
> You can just checkout that commit: git checkout HEAD@{27}
>
> or reset to that commit: git reset HEAD@{27}
Personally I advise against using git reset except when you *really*
In general, if you stay away from destructive operations, git is quite
safe. If you find yourself wanting to perform a destructive
operation, make sure first that any extant changes in your workspace
are committed so that you can always get them back from the reflog.
Committing stuff you don't
On Thu, Oct 17, 2013 at 8:11 PM, Cyrille Artho wrote:
> I once made a mistake with git, too, that took a while to recover.
>
> IMHO git works well if
>
> (1) You are very careful and RTFM closely before using "reset", "rebase".
Rebase is not destructive: your commits remain
On Thu, Oct 17, 2013 at 8:02 PM, Vincent van Ravesteijn <v...@lyx.org> wrote:
> Nico Williams schreef op 18-10-2013 0:59:
>
> The ironic thing using Git is that it is very safe if and only if you know
> your way around with Git. I remember that when I started using Git, I
>
On Fri, May 10, 2013 at 12:45 PM, Richard Heck rgh...@lyx.org wrote:
The only significant worry here concerns stability: Could a Qt update break
us? We already depend heavily on Qt, so this is not as large a concern as
with depending upon other external libraries. And my sense is that these
On Fri, May 10, 2013 at 12:45 PM, Richard Heck wrote:
> The only significant worry here concerns stability: Could a Qt update break
> us? We already depend heavily on Qt, so this is not as large a concern as
> with depending upon other external libraries. And my sense is that
On Thu, May 9, 2013 at 8:21 AM, Alex Vergara Gil a...@cphr.edu.cu wrote:
First of all, This is a very old feature request that will be greatly
appreciated at least from my part!
Me too.
I think there are much work done in this sense, please read Nico Williams'
approach. I think
On Thu, May 9, 2013 at 4:27 PM, Richard Heck rgh...@lyx.org wrote:
The LyX document is internally a (very complex) tree structure, so I think
this is pretty simple. As Jose mentioned, Lars has the write side of it
pretty much done a long time ago. My sense is that it was so long ago that
it
I should add that while *writing* XML is easy enough (valid XML too),
it's reading that's hard, so you can't avoid using a library.
On Thu, May 9, 2013 at 8:21 AM, Alex Vergara Gil <a...@cphr.edu.cu> wrote:
> First of all, This is a very old feature request that will be greatly
> appreciated at least from my part!
Me too.
> I think there are much work done in this sense, please read Nico Williams'
>
On Thu, May 9, 2013 at 4:27 PM, Richard Heck wrote:
> The LyX document is internally a (very complex) tree structure, so I think
> this is pretty simple. As Jose mentioned, Lars has the write side of it
> pretty much done a long time ago. My sense is that it was so long ago that
>
I should add that while *writing* XML is easy enough (valid XML too),
it's reading that's hard, so you can't avoid using a library.
Reading will be easier, I think, for the reasons I've described before.
Also, you could use lyx2xml to write so you can test the read path, but I
don't know of an xml2lyx tool you could use for the reverse.
Just my 2c.
Reading will be easier, I think, for the reasons I've described before.
Also, you could use lyx2xml to write so you can test the read path, but I
don't know of an xml2lyx tool you could use for the reverse.
Just my 2c.
On Thu, May 2, 2013 at 2:01 PM, Tommaso Cucinotta tomm...@lyx.org wrote:
As an immediate concern, adding to Pavel's ones, I have to say that I'm not
so sure that merging different edits on the .lyx file level, very much like a
version control system would do in presence of concurrent commits,
On Thu, May 2, 2013 at 2:22 PM, Richard Heck rgh...@lyx.org wrote:
On 05/02/2013 03:16 PM, Nico Williams wrote:
On Thu, May 2, 2013 at 2:01 PM, Tommaso Cucinotta tomm...@lyx.org wrote:
As an immediate concern, adding to Pavel's ones, I have to say that I'm
not
so sure that merging different
On Thu, May 2, 2013 at 2:01 PM, Tommaso Cucinotta wrote:
> As an immediate concern, adding to Pavel's ones, I have to say that I'm not
> so sure that merging different edits on the .lyx file level, very much like a
> version control system would do in presence of concurrent
On Thu, May 2, 2013 at 2:22 PM, Richard Heck <rgh...@lyx.org> wrote:
> On 05/02/2013 03:16 PM, Nico Williams wrote:
>>
>> On Thu, May 2, 2013 at 2:01 PM, Tommaso Cucinotta <tomm...@lyx.org> wrote:
>>>
>>> As an immediate concern, adding to Pavel's one
On Tue, Apr 30, 2013 at 2:49 AM, Liviu Andronic landronim...@gmail.com wrote:
I must admit that I share Pavel's sentiment: I'm not sure how much the
community needs/requires a chatting function in LyX. But I was
thinking of possibly a cheap workaround: Why not communicate with
images?
LyX
On Tue, Apr 30, 2013 at 3:26 AM, Tommaso Cucinotta tomm...@lyx.org wrote:
On 30/04/13 00:23, Nico Williams wrote:
Well... If a paragraph is deleted then the pointer might get assigned
in a subsequent allocation and... you end up with an aliasing problem.
I was thinking of detecting
On Tue, Apr 30, 2013 at 3:41 PM, Tommaso Cucinotta tomm...@lyx.org wrote:
On 30/04/13 10:51, Nico Williams wrote:
Part of the XMPP/whatever fabric gets disconnected from the rest. Now
you have two LyX instances collaborating but unable to reach each
other. What do you do now? If each user
On Tue, Apr 30, 2013 at 2:49 AM, Liviu Andronic wrote:
> I must admit that I share Pavel's sentiment: I'm not sure how much the
> community needs/requires a chatting function in LyX. But I was
> thinking of possibly a cheap workaround: Why not communicate with
> images?
On Tue, Apr 30, 2013 at 3:26 AM, Tommaso Cucinotta <tomm...@lyx.org> wrote:
> On 30/04/13 00:23, Nico Williams wrote:
>> Well... If a paragraph is deleted then the pointer might get assigned
>> in a subsequent allocation and... you end up with an aliasing problem.
>
>
On Tue, Apr 30, 2013 at 3:41 PM, Tommaso Cucinotta <tomm...@lyx.org> wrote:
> On 30/04/13 10:51, Nico Williams wrote:
>> Part of the XMPP/whatever fabric gets disconnected from the rest. Now
>> you have two LyX instances collaborating but unable to reach each
>>
On Sat, Apr 20, 2013 at 7:06 AM, Vinícius dos Santos Oliveira
vini.ipsma...@gmail.com wrote:
2013/4/20 Tommaso Cucinotta tomm...@lyx.org
3) client-side encryption add-on: can we exchange b64 encoding of
client-side
encrypted text segments, so that IM servers cannot see what's being
On Sat, Apr 20, 2013 at 5:33 AM, Tommaso Cucinotta tomm...@lyx.org wrote:
Concerning the interactive editing, I also remembered some critical issues
faced
during my prior quick hack: LyX internally uses index positions for the
cursor,
i.e., my cursor is on the 3rd paragraph, 5th character,
On Mon, Apr 29, 2013 at 6:06 PM, Tommaso Cucinotta tomm...@lyx.org wrote:
On 29/04/13 23:26, Nico Williams wrote:
It's possible to use OTR:
http://en.wikipedia.org/wiki/Off-the-Record_Messaging
Yes. Let libpurple (or similar) take care of this for you.
Are you aware of a similar library
On Mon, Apr 29, 2013 at 6:03 PM, Tommaso Cucinotta tomm...@lyx.org wrote:
On 29/04/13 23:32, Nico Williams wrote:
However, when considering that other users might be editing stuff
above/before our
cursor position, then it means this way of referencing positions within the
text
should
On Mon, Apr 29, 2013 at 6:21 PM, Tommaso Cucinotta tomm...@lyx.org wrote:
On 30/04/13 00:11, Nico Williams wrote:
But do you want to reuse an OTR
implementation?
The question is why OTR, but perhaps the answer is simply that is already
made to be compatible with messaging protocols.
OTR
BTW, this has all been solved before (clearly). Research it and use
whatever protocol pattern is most appropriate (or, if you can't
because of patents, invent a new protocol).
Some posts on this list pointed at some such prior work.
On Sat, Apr 20, 2013 at 7:06 AM, Vinícius dos Santos Oliveira
wrote:
> 2013/4/20 Tommaso Cucinotta
>>
>> 3) client-side encryption add-on: can we exchange b64 encoding of
>> client-side
>>encrypted text segments, so that IM servers cannot see what's
On Sat, Apr 20, 2013 at 5:33 AM, Tommaso Cucinotta wrote:
> Concerning the interactive editing, I also remembered some critical issues
> faced
> during my prior quick hack: LyX internally uses index positions for the
> cursor,
> i.e., my cursor is on the 3rd paragraph, 5th
On Mon, Apr 29, 2013 at 6:06 PM, Tommaso Cucinotta <tomm...@lyx.org> wrote:
> On 29/04/13 23:26, Nico Williams wrote:
>>> It's possible to use OTR:
>>> http://en.wikipedia.org/wiki/Off-the-Record_Messaging
>>
>> Yes. Let libpurple (or similar) take
On Mon, Apr 29, 2013 at 6:03 PM, Tommaso Cucinotta <tomm...@lyx.org> wrote:
> On 29/04/13 23:32, Nico Williams wrote:
>>> However, when considering that other users might be editing stuff
>>> above/before our
>>> cursor position, then it means this
On Mon, Apr 29, 2013 at 6:21 PM, Tommaso Cucinotta <tomm...@lyx.org> wrote:
> On 30/04/13 00:11, Nico Williams wrote:
>> But do you want to reuse an OTR
>> implementation?
>
> The question is why OTR, but perhaps the answer is simply that is already
> made t
BTW, this has all been solved before (clearly). Research it and use
whatever protocol pattern is most appropriate (or, if you can't
because of patents, invent a new protocol).
Some posts on this list pointed at some such prior work.
On Wed, Apr 24, 2013 at 4:40 PM, Guenter Milde mi...@users.sf.net wrote:
On 2013-04-23, Zahari Dim wrote:
On the LyX side, adding reStructuredText as one export format could be
sensible. Again, this would not be ready for round-trips.
This means it might be easier to use XML as intermediate
On Wed, Apr 24, 2013 at 4:40 PM, Guenter Milde wrote:
> On 2013-04-23, Zahari Dim wrote:
> On the LyX side, adding reStructuredText as one export format could be
> sensible. Again, this would not be ready for round-trips.
>
> This means it might be easier to use XML as
On Monday, April 15, 2013, Jean-Marc Lasgouttes wrote:
15/04/2013 13:54, William Adams:
I guess the best solution would be for QT to become friendly to screen
readers, but that's out-of-scope.
Actually, the WorkArea is completely curtom, not under the control of Qt.
So we would have to
On Monday, April 15, 2013, Jean-Marc Lasgouttes wrote:
> 15/04/2013 13:54, William Adams:
>
>> I guess the best solution would be for QT to become friendly to screen
>> readers, but that's out-of-scope.
>>
>
> Actually, the WorkArea is completely curtom, not under the control of Qt.
> So we would
On Sunday, April 14, 2013, Guenter Milde wrote:
On 2013-04-13, Fernando Botelho wrote:
I consider TeX and LaTeX, a potentially extremely useful technology for
the blind, because it can allow wonderful formatting even for someone
who is blind. LYX, or the idea of accessing the power of
On Sunday, April 14, 2013, Guenter Milde wrote:
> On 2013-04-13, Fernando Botelho wrote:
> > I consider TeX and LaTeX, a potentially extremely useful technology for
> > the blind, because it can allow wonderful formatting even for someone
> > who is blind. LYX, or the idea of accessing the power
On Thu, Apr 11, 2013 at 12:34 AM, Pavel Sanda sa...@lyx.org wrote:
Nico Williams wrote:
I see the smiley. I hope to convince you to stop the use of RCS :)
Then you will need to show better arguments :) I was talking about single
lyx documents 50-400 pages, not about linux kernel.
I'm really
On Thu, Apr 11, 2013 at 1:42 AM, Pavel Sanda sa...@lyx.org wrote:
Nico Williams wrote:
Indeed. I just want LyX to not ever run a git checkout command. Not
This is between you and Georg :)
limit itself to informational actions only in the case of git-like
VCSes (Mercurial, Fossil
On Thu, Apr 11, 2013 at 8:46 AM, Richard Heck rgh...@lyx.org wrote:
On 04/11/2013 08:45 AM, Elias Assarsson wrote:
Here's a quick guide to how the export routines work. Basically, it starst
at Buffer::makeLyXHTMLFile(), which just sets up a file stream, does some
preliminary configuration, and
Here's my (8), really my #1: 3-way diff/merge support.
On Thu, Apr 11, 2013 at 2:42 PM, Georg Baum
georg.b...@post.rwth-aachen.de wrote:
No. I don't want LyX to run any checkout command. I do not even need the
simple checkout with svn that Pavel uses. If you look into the sources you
can see that the VCS states VCS::LOCKED and VCS::UNLOCKED are not
On Thu, Apr 11, 2013 at 12:34 AM, Pavel Sanda <sa...@lyx.org> wrote:
> Nico Williams wrote:
>> I see the smiley. I hope to convince you to stop the use of RCS :)
>
> Then you will need to show better arguments :) I was talking about single
> lyx documents 50-400 pages
On Thu, Apr 11, 2013 at 1:42 AM, Pavel Sanda <sa...@lyx.org> wrote:
> Nico Williams wrote:
>> Indeed. I just want LyX to not ever run a git checkout command. Not
>
> This is between you and Georg :)
>
>> limit itself to informational actions only in the case o
On Thu, Apr 11, 2013 at 8:46 AM, Richard Heck wrote:
> On 04/11/2013 08:45 AM, Elias Assarsson wrote:
> Here's a quick guide to how the export routines work. Basically, it starst
> at Buffer::makeLyXHTMLFile(), which just sets up a file stream, does some
> preliminary
Here's my (8), really my #1: 3-way diff/merge support.
On Thu, Apr 11, 2013 at 2:42 PM, Georg Baum
wrote:
> No. I don't want LyX to run any checkout command. I do not even need the
> simple checkout with svn that Pavel uses. If you look into the sources you
> can see that the VCS states VCS::LOCKED and VCS::UNLOCKED
On Wed, Apr 10, 2013 at 2:52 AM, Tommaso Cucinotta tomm...@lyx.org wrote:
This means we're not in a workspace.
It doesn't seem like that, from my exps:
// both README and README.xx exist on FS
tommaso@mobiletom:~/lyx-trunk-ws/lyx$ git status --porcelain README
Would it be easier/better to have XML export and then use XSLT for
XHTML/HTML/CSS and ePub conversions?
Using XML as a go-between would require doing something about defining
a stable schema, explicit or otherwise. I've a Python script to
convert .lyx to XML with an implicit schema, but it's no
On Wed, Apr 10, 2013 at 4:37 PM, Adrián Pereira adrian.pere...@udc.es wrote:
Absolutely, i didn't know about XSLT.
i'm actually forking lyx. Then i'll take a look at the code in the repo.
So, the problem is to find a schema for doing the translation between .lyx
and XML. If you have a Python
I should add that I'm willing to help you familiarize yourself with
XSLT, answer XSLT questions and so on. Then you might be better
informed about how to attack this problem. You'd still need to talk
to a proper LyX mentor.
Nico
--
On Wed, Apr 10, 2013 at 8:22 PM, Tommaso Cucinotta tomm...@lyx.org wrote:
On 10/04/13 00:26, Nico Williams wrote:
But again, git ls-files seems WAY EASIER.
This will tell you if a file is tracked, not whether it has unstaged
or uncommitted changes.
Ok, let me be sure of one thing: the usage
On Wed, Apr 10, 2013 at 7:46 PM, Pavel Sanda sa...@lyx.org wrote:
The project listed in GSoC intended 3) and perhaps fix 1. It wouldn't
be wise to create completely new export routines and my hope is that
routines in 2) can be reused in large part with perhaps few switches.
It might well be
On Wed, Apr 10, 2013 at 11:30 PM, Pavel Sanda sa...@lyx.org wrote:
Nico Williams wrote:
But standalone RCS or SCCS is (should be!) a rarity now -- so early
90s! no, so 70s! :) I'd encourage you to encourage your users to
switch to a modern VCS and drop the RCS code.
On contrary! :) I still
On Wed, Apr 10, 2013 at 2:52 AM, Tommaso Cucinotta wrote:
> > This means we're not in a workspace.
>
> It doesn't seem like that, from my exps:
>
> // both README and README.xx exist on FS
> tommaso@mobiletom:~/lyx-trunk-ws/lyx$ git status --porcelain README
>
Would it be easier/better to have XML export and then use XSLT for
XHTML/HTML/CSS and ePub conversions?
Using XML as a go-between would require doing something about defining
a stable schema, explicit or otherwise. I've a Python script to
convert .lyx to XML with an implicit schema, but it's no
On Wed, Apr 10, 2013 at 4:37 PM, Adrián Pereira wrote:
> Absolutely, i didn't know about XSLT.
> i'm actually forking lyx. Then i'll take a look at the code in the repo.
> So, the problem is to find a schema for doing the translation between .lyx
> and XML. If you have a
I should add that I'm willing to help you familiarize yourself with
XSLT, answer XSLT questions and so on. Then you might be better
informed about how to attack this problem. You'd still need to talk
to a proper LyX mentor.
Nico
--
On Wed, Apr 10, 2013 at 8:22 PM, Tommaso Cucinotta <tomm...@lyx.org> wrote:
> On 10/04/13 00:26, Nico Williams wrote:
>>> But again, git ls-files seems WAY EASIER.
>>
>> This will tell you if a file is tracked, not whether it has unstaged
>> or uncommitted ch
On Wed, Apr 10, 2013 at 7:46 PM, Pavel Sanda wrote:
> The project listed in GSoC intended 3) and perhaps fix 1. It wouldn't
> be wise to create completely new export routines and my hope is that
> routines in 2) can be reused in large part with perhaps few switches.
It might well
On Wed, Apr 10, 2013 at 11:30 PM, Pavel Sanda <sa...@lyx.org> wrote:
> Nico Williams wrote:
>> But standalone RCS or SCCS is (should be!) a rarity now -- so early
>> 90s! no, so 70s! :) I'd encourage you to encourage your users to
>> switch to a modern VCS and drop th
Since we're piling on...
I don't mind the sort of ribbon menu as they've evolved to be at MSFT,
but I do prefer pull-down menus with *text* instead of icons. I'm a
textual user, I prefer everything as textual as possible. I'd even
like a search feature for menus/functions, and in general I'd
On Tue, Apr 9, 2013 at 1:36 PM, Liviu Andronic landronim...@gmail.com wrote:
On Tue, Apr 9, 2013 at 8:20 PM, Nico Williams n...@cryptonector.com wrote:
textual user, I prefer everything as textual as possible. I'd even
like a search feature for menus/functions, and in general I'd like
That's
On Tue, Apr 9, 2013 at 6:05 PM, Tommaso Cucinotta tomm...@lyx.org wrote:
Ok, really really wanting to use git status --porcelain, we can go for the
following (but I hate it).
Let me write it in shell code:
I guess I can't get you to give up on this :(
:)
So, to find out if a path is in a
On Tue, Apr 9, 2013 at 6:26 PM, Nico Williams n...@cryptonector.com wrote:
So, to wrap up, I think you want:
fork(), chdir() to the directory containing the file, exec() git
status --porcelain, and parse the result in the parent process (read
via a pipe), then display the status (for each
Since we're piling on...
I don't mind the sort of ribbon menu as they've evolved to be at MSFT,
but I do prefer pull-down menus with *text* instead of icons. I'm a
textual user, I prefer everything as textual as possible. I'd even
like a search feature for menus/functions, and in general I'd
On Tue, Apr 9, 2013 at 1:36 PM, Liviu Andronic <landronim...@gmail.com> wrote:
> On Tue, Apr 9, 2013 at 8:20 PM, Nico Williams <n...@cryptonector.com> wrote:
>> textual user, I prefer everything as textual as possible. I'd even
>> like a search feature for menus/functio
On Tue, Apr 9, 2013 at 6:05 PM, Tommaso Cucinotta wrote:
> Ok, really really wanting to use git status --porcelain, we can go for the
> following (but I hate it).
> Let me write it in shell code:
I guess I can't get you to give up on this :(
:)
So, to find out if a path is in
On Tue, Apr 9, 2013 at 6:26 PM, Nico Williams <n...@cryptonector.com> wrote:
> So, to wrap up, I think you want:
>
> fork(), chdir() to the directory containing the file, exec() git
> status --porcelain, and parse the result in the parent process (read
> via a pipe), th
On Tue, Apr 2, 2013 at 2:19 PM, Georg Baum
georg.b...@post.rwth-aachen.de wrote:
There are three (minor IMHO) drawbacks:
1) The LaTeX detection for pasting is a heuristic and may fail in some
cases. If that happens, tex2lyx is run on text that is not really LaTeX, and
this may give unexpected
On Mon, Apr 8, 2013 at 3:34 PM, Jean-Marc Lasgouttes lasgout...@lyx.org wrote:
We could have a paste-special menu entry that opens a dialog with the
text-as-line and text-as-paragraph options too.
+1. Tasting content-type is error-prone (but an OK default for ^V);
the user likely knows the
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 of
those that have side
On Mon, Apr 8, 2013 at 4:22 PM, Tommaso Cucinotta tomm...@lyx.org wrote:
On 04/04/13 03:03, Nico Williams wrote:
...
It looks like you'd like LyX to launch gitk! Why repeating all that stuff
within LyX :-)?
Actually, I want LyX to do *nothing* with git *except*, maybe, tell me
if any file
On Tue, Apr 2, 2013 at 2:19 PM, Georg Baum
wrote:
> There are three (minor IMHO) drawbacks:
>
> 1) The LaTeX detection for pasting is a heuristic and may fail in some
> cases. If that happens, tex2lyx is run on text that is not really LaTeX, and
> this may give
On Mon, Apr 8, 2013 at 3:34 PM, Jean-Marc Lasgouttes wrote:
> We could have a paste-special menu entry that opens a dialog with the
> text-as-line and text-as-paragraph options too.
+1. Tasting content-type is error-prone (but an OK default for ^V);
the user likely knows the
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 of
those that have side
On Mon, Apr 8, 2013 at 4:22 PM, Tommaso Cucinotta <tomm...@lyx.org> wrote:
> On 04/04/13 03:03, Nico Williams wrote:
> > ...
> It looks like you'd like LyX to launch gitk! Why repeating all that stuff
> within LyX :-)?
Actually, I want LyX to do *nothing* with git *except*,
On Apr 3, 2013 6:58 PM, Pavel Sanda sa...@lyx.org 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.
I'm hard-pressed to think of git-specific behavior in LyX that i want
besides
1 - 100 of 153 matches
Mail list logo