On Sun, May 19, 2019 at 03:00:01PM +0200, Jürgen Womser-Schütz wrote:
> For me the LyX build is broken:
>
> CXX Cursor.o
> Cursor.cpp: In member function ‘bool lyx::Cursor::macroModeClose(bool)’:
> Cursor.cpp:1765:53: error: expected ‘)’ before ‘{’ token
> if (!selection.empty() && data
For me the LyX build is broken:
CXX Cursor.o
Cursor.cpp: In member function ‘bool lyx::Cursor::macroModeClose(bool)’:
Cursor.cpp:1765:53: error: expected ‘)’ before ‘{’ token
if (!selection.empty() && data && data->numargs() {
^
Cursor
On 19 January 2017 at 23:58, Pavel Sanda wrote:
> Christian Ridderström wrote:
> > When a CI job is using e-mail notifications, there's an option to in
> > addition to e-mailing the devel-list, also e-mail individuals who
> recently
> > committed. Do we want that?
>
> I think it's better to use o
Christian Ridderström wrote:
> When a CI job is using e-mail notifications, there's an option to in
> addition to e-mailing the devel-list, also e-mail individuals who recently
> committed. Do we want that?
I think it's better to use only lyx-devel and let people sort it out
rather than spam peopl
ere's the description of the option:
If this option is checked, the notification e-mail will be sent to
individuals who have committed changes for the broken build (by assuming
that those changes broke the build).
If e-mail addresses are also specified in the recipient list, then both the
indi
