headers
Uwe Stöhr | 3 Jan 2010 00:31
Picon

SVN broken - was: Re: [patch] Automated formatting of Keytest bug reports.

 > i have commited the patch. hopefully without errs, but rather check it ;)

This commit breaks SVN completely: SVN cleanup doesn't help and also no completely new checkout.

The reason is that you committed a file named "view:1" This is an invlaid filename on Windows and 
thus screws up SVN. Can anybody on Linux please rename the file so that has no "\", "/", ":", "|" 
"?", "*", "<", ">" and '"' in its name.

thanks and regards
Uwe

p.s. A happy new year to all of you LyXers
Permalink | Reply | 3 comments |
headers
Pavel Sanda | 3 Jan 2010 00:35
Favicon

Re: SVN broken - was: Re: [patch] Automated formatting of Keytest bug reports.

Uwe Stöhr wrote:
> > i have commited the patch. hopefully without errs, but rather check it ;)
>
> This commit breaks SVN completely: SVN cleanup doesn't help and also no 
> completely new checkout.

ouch. can you try whether svn works now?
pavel
Permalink | Reply | 1 comment |
headers
John McCabe-Dansted | 3 Jan 2010 02:22
Picon

Re: SVN broken - was: Re: [patch] Automated formatting of Keytest bug reports.

On Sun, Jan 3, 2010 at 7:31 AM, Uwe Stöhr <uwestoehr@...> wrote:
> The reason is that you committed a file named "view:1" This is an invlaid
> filename on Windows and thus screws up SVN. Can anybody on Linux please
> rename the file so that has no "\", "/", ":", "|" "?", "*", "<", ">" and '"'
> in its name.

Sorry.

Hmm, apparently SVN allowing ":"'s to be committed is a known problem
and precommit hooks is the approved solution.
   http://subversion.tigris.org/issues/show_bug.cgi?id=1277

I am a little surprised that SVN doesn't ban ":" by default, given
that it breaks checkout.

--

-- 
John C. McCabe-Dansted
Permalink | Reply | 0 comments |
headers
Abdelrazak Younes | 3 Jan 2010 10:24
Favicon

Re: r32653 - lyx-devel/trunk/src/frontends/qt4

On 27/12/2009 11:03, kuemmel@... wrote:
> Author: kuemmel
> Date: Sun Dec 27 11:03:16 2009
> New Revision: 32653
> URL: http://www.lyx.org/trac/changeset/32653
>
> Log:
> no duplicated success messages: one connection is enough
>
> Modified:
>     lyx-devel/trunk/src/frontends/qt4/GuiView.cpp
>
> Modified: lyx-devel/trunk/src/frontends/qt4/GuiView.cpp
> ==============================================================================
> --- lyx-devel/trunk/src/frontends/qt4/GuiView.cpp	Sun Dec 27 00:58:24 2009	(r32652)
> +++ lyx-devel/trunk/src/frontends/qt4/GuiView.cpp	Sun Dec 27 11:03:16 2009	(r32653)
>  <at>  <at>  -277,8 +277,6  <at>  <at> 
>   		if (preview_watcher_.isRunning())
>   			preview_watcher_.waitForFinished();
>   		preview_watcher_.setFuture(f);
> -		connect(&preview_watcher_, SIGNAL(finished()), gv_,
> -			SLOT(threadFinished()));
>   	}
>   #endif
>
>  <at>  <at>  -374,6 +372,8  <at>  <at> 
>   #if (QT_VERSION>= 0x040400)
>   	connect(&d.autosave_watcher_, SIGNAL(finished()), this,
>   		SLOT(threadFinished()));
> +	connect(&d.preview_watcher_, SIGNAL(finished()), this,
(Continue reading)

Permalink | Reply | 0 comments |
headers
Abdelrazak Younes | 3 Jan 2010 10:38
Favicon

Re: r32678 - in lyx-devel/trunk/src: . frontends frontends/qt4

On 02/01/2010 03:07, Vincent van Ravesteijn wrote:
> Tommaso Cucinotta schreef:
>
>>>> However, in order to implement this, I would need to call the
>>>>
>>>>  GuiWorkArea * GuiView::workArea(Buffer & buffer)
>> on a related note, what is the "Buffer::gui_" field ? What is the 
>> purpose of those "gui delegate" ? If I call "hasGuiDelegate()", is 
>> that equivalent to checking that the buffer has an associated view 
>> (workarea and bufferview) ?
>
> I can't explain what the bufferGuiDelegate and the 
> BufferViewGuiDelegate exactly do, but you can see in 
> src\frontends\Delegates.h what kind of info is passed to the frontend.

Those are just there to mimic signal/slot connections from Buffer 
(changed() and message() signals) to GuiWorkArea and GuiView. Previously 
we used boost::signals then André removed this and we created those 
delegates in replacement because Qt signals were forbidden at this time. 
Last meeting we agreed that we may allow QtCore stuff in the core so the 
correct thing to do would be to make those Buffer signals Qt signals. 
Anyone interested?

IOW this also means "Don't use this information!" as this is going to 
disappear sooner or later :-)

Abdel
Permalink | Reply | 0 comments |
headers
Abdelrazak Younes | 3 Jan 2010 10:40
Favicon

Oh and by the way...

Happy new year to you all and your respective families!

Abdel.
Permalink | Reply | 1 comment |
headers
Abdelrazak Younes | 3 Jan 2010 12:10
Favicon

Assertion in trunk when trying to export Math manual to LyX HTML

H Richard,

I guess this is for you :-)

      LyX.exe!lyx::doAssert(const char * expr=0x01f22720, const char * 
file=0x01f226e8, long line=212)  Ligne 23    C++
      LyX.exe!lyx::InsetMathDecoration::mathmlize(lyx::MathStream & 
os={...})  Ligne 212 + 0x5e octets    C++
 >    LyX.exe!lyx::mathmlize(const lyx::MathData & dat={...}, 
lyx::MathStream & os={...})  Ligne 1431 + 0x31 octets    C++
      LyX.exe!lyx::operator<<(lyx::MathStream & ms={...}, const 
lyx::MathData & ar={...})  Ligne 288 + 0xd octets    C++
      LyX.exe!lyx::InsetMathGrid::mathmlize(lyx::MathStream & os={...})  
Ligne 981 + 0x45 octets    C++
      LyX.exe!lyx::InsetMathHull::xhtml(lyx::XHTMLStream & xs={...}, 
const lyx::OutputParams & __formal={...})  Ligne 1786    C++
      LyX.exe!lyx::Paragraph::simpleLyXHTMLOnePar(const lyx::Buffer & 
buf={...}, lyx::XHTMLStream & xs={...}, const lyx::OutputParams & 
runparams={...}, const lyx::Font & outerfont={...}, bool fortoc=false, 
int initial=0)  Ligne 2452 + 0x2a octets    C++
      LyX.exe!lyx::`anonymous namespace'::makeParagraphs(const 
lyx::Buffer & buf={...}, lyx::XHTMLStream & xs={...}, const 
lyx::OutputParams & runparams={...}, const lyx::Text & text={...}, const 
std::list<lyx::Paragraph,std::allocator<lyx::Paragraph> 
 >::_Const_iterator<1> & pbegin={itemdepth=0 d=0x085a3cf0 }, const 
std::list<lyx::Paragraph,std::allocator<lyx::Paragraph> 
 >::_Const_iterator<1> & pend={itemdepth='Í' d=0xcdcdcdcd })  Ligne 572 
+ 0x8d octets    C++
      LyX.exe!lyx::xhtmlParagraphs(const lyx::Text & text={...}, const 
lyx::Buffer & buf={...}, lyx::XHTMLStream & xs={...}, const
(Continue reading)

Permalink | Reply | 1 comment |
headers
Pavel Sanda | 3 Jan 2010 12:34
Favicon

Warning for neglected file lock release

hi,

i would like to introduce new rc for some kind of pop-up (unset by default) which would
warn about unreleased file lock when working with version control.
any objections?

pavel
Permalink | Reply | 6 comments |
headers
Vincent van Ravesteijn | 3 Jan 2010 12:45
Picon
Picon

Re: Warning for neglected file lock release

Pavel Sanda schreef:
> hi,
>
> i would like to introduce new rc for some kind of pop-up (unset by default) which would
> warn about unreleased file lock when working with version control.
> any objections?
>
> pavel
>   
It feels like it is a bit too specific to have a new rc value just for 
showing a warning that only effects a specific case that I don't even 
understand that can only happen when using a feature which is probably 
only used by you.

Why don't you add the checkbox "Do not show this warning again", to the 
waring message ?

Vincent
Permalink | Reply | 5 comments |
headers
Christian Rutkowski | 1 Jan 2010 13:07
Picon
Picon

Trouble with KDVI file corruption error message

Dear developers of Lyx,

since many years I used my old notebook with Lyx 1.3.2 running under SUSE Linux and I really liked it and used
it a lot, to write letters, scripts for lessons and more. Now I got a new notebook running a RedHat Fedora
Linux, but without Lyx :-((

So I got Lyx 1.6.4.2 (and Qt 4.6.0) from the Internet some weeks ago and yesterday I got it compiled, linked,
and up and running. This really worked fine, thanks to the INSTALL instructions that helped me to get over
the error messages from ./config that it could not find the Qt4 library.

Trying the new version, I was pleased. There is just one point that makes me worry, but I am not really sure if
this is a bug in Lyx or KDVI: If I start a DVI preview (using the tool bar button or the menu), KDVI starts. If it
encounters two adjacent "Umlaute", such as 'ü' and 'ß' in the German word 'Grüße', it stops with an
error message that "KDVI had trouble interpreting your DVI file. Most likely this means that the DVI file
is broken". In addition it says "The unknown op-code 129 was encountered". In some occasions, I get this
error message even with a single character 'ü', but I always get it from an arbitrary combination of two
such characters, such as 'Ä', 'ä', 'Ö', 'ö', 'Ü', or 'ü'. PDF output works fine, Acrobat Reader
perfectly reads the file produced. I attach both a sample Lyx
  file and the DVI file, perhaps this helps you if there should be a bug in Lyx.

Best wishes to you and yours for 2010!

Kind regards
Christian Rutkowski
--

-- 
Preisknaller: GMX DSL Flatrate für nur 16,99 Euro/mtl.!
http://portal.gmx.net/de/go/dsl02
Attachment (MeinBrief.lyx): application/x-lyx, 4081 bytes
Attachment (MeinBrief.dvi): application/x-dvi, 1204 bytes
(Continue reading)

Permalink | Reply | 2 comments |

Gmane