Build failed in Jenkins: Build branch "master" » ubuntu-xenial-qt4-autotools-extended #368

[ci-lyx]

https://ci.inria.fr/lyx/job/build-master-head/job/ubuntu-xenial-qt4-autotools-extended/368/--
Started by an SCM change
Building remotely on lyx-linux6 (linux) in workspace 

[WS-CLEANUP] Deleting project workspace...
Cloning the remote Git repository
Using shallow clone
Avoid fetching tags
Honoring refspec on initial clone
Cloning repository git://git.lyx.org/lyx.git
 > git init 
 > 
 >  # timeout=10
Fetching upstream changes from git://git.lyx.org/lyx.git
 > git --version # timeout=10
 > git fetch --no-tags --progress git://git.lyx.org/lyx.git 
 > +refs/heads/*:refs/remotes/origin/* --depth=1
 > git config remote.origin.url git://git.lyx.org/lyx.git # timeout=10
 > git config --add remote.origin.fetch +refs/heads/*:refs/remotes/origin/* # 
 > timeout=10
 > git config remote.origin.url git://git.lyx.org/lyx.git # timeout=10
Fetching upstream changes from git://git.lyx.org/lyx.git
 > git fetch --no-tags --progress git://git.lyx.org/lyx.git 
 > +refs/heads/*:refs/remotes/origin/* --depth=1
 > git rev-parse refs/remotes/origin/master^{commit} # timeout=10
 > git rev-parse refs/remotes/origin/refs/heads/master^{commit} # timeout=10
Checking out Revision ddf2c2a9d437a1d6d1079e837a71154bd844d304 
(refs/remotes/origin/master)
 > git config core.sparsecheckout # timeout=10
 > git checkout -f ddf2c2a9d437a1d6d1079e837a71154bd844d304
 > git rev-list 4c4db93645430160b13d2ed1b27fead2e1f87db3 # timeout=10
First time build. Skipping changelog.
[ubuntu-xenial-qt4-autotools-extended] $ /bin/sh -xe 
/tmp/hudson4541201546724896870.sh
+ IMAGE=lyxproject/build-lyx-using-ubuntu-xenial-qt4-autotools
+ C_BUILD=/build
+ C_WS=/build/workspace
+ C_SCRIPT=/build/build_lyx_extended.sh
+ docker run --rm -v 
:/build/workspace
 lyxproject/build-lyx-using-ubuntu-xenial-qt4-autotools 
/build/build_lyx_extended.sh /build/workspace
# Executing: cd /build/workspace
# Executing: ./autogen.sh
./autogen.sh: 11: ./autogen.sh: automake (GNU automake) 1.15: not found
LyX requires automake >= 1.14
Command './autogen.sh' failed, exiting
Build step 'Execute shell' marked build as failure

Re: Fix for vertical table border for added column

[racoon]

On 21.08.2017 23:32, Kornel Benko wrote:

Am Montag, 21. August 2017 um 22:24:10, schrieb racoon 

Playing with the new settings now ...
It is somehow requiring getting used to ... but I like it.


I am not sure I follow. What "new settings"?

Daniel


I am able to set arbitrary borders with the table toolbar, but
with the tabular settings dialog it is often not possible.

Kornel



Sorry, I am slow. I still don't know what you mean. Is that something 
related to my patch of the add row/column or set all borders table toolbar?


Daniel

Build failed in Jenkins: Build branch "master" » ubuntu-xenial-qt4-autotools #358

[ci-lyx]

https://ci.inria.fr/lyx/job/build-master-head/job/ubuntu-xenial-qt4-autotools/358/--
Started by an SCM change
Building remotely on lyx-linux1 (linux) in workspace 

[WS-CLEANUP] Deleting project workspace...
[WS-CLEANUP] Done
Cloning the remote Git repository
Using shallow clone
Avoid fetching tags
Honoring refspec on initial clone
Cloning repository git://git.lyx.org/lyx.git
 > git init 
 > 
 >  # timeout=10
Fetching upstream changes from git://git.lyx.org/lyx.git
 > git --version # timeout=10
 > git fetch --no-tags --progress git://git.lyx.org/lyx.git 
 > +refs/heads/*:refs/remotes/origin/* --depth=1
 > git config remote.origin.url git://git.lyx.org/lyx.git # timeout=10
 > git config --add remote.origin.fetch +refs/heads/*:refs/remotes/origin/* # 
 > timeout=10
 > git config remote.origin.url git://git.lyx.org/lyx.git # timeout=10
Fetching upstream changes from git://git.lyx.org/lyx.git
 > git fetch --no-tags --progress git://git.lyx.org/lyx.git 
 > +refs/heads/*:refs/remotes/origin/* --depth=1
 > git rev-parse refs/remotes/origin/master^{commit} # timeout=10
 > git rev-parse refs/remotes/origin/refs/heads/master^{commit} # timeout=10
Checking out Revision ddf2c2a9d437a1d6d1079e837a71154bd844d304 
(refs/remotes/origin/master)
 > git config core.sparsecheckout # timeout=10
 > git checkout -f ddf2c2a9d437a1d6d1079e837a71154bd844d304
 > git rev-list 4c4db93645430160b13d2ed1b27fead2e1f87db3 # timeout=10
First time build. Skipping changelog.
[ubuntu-xenial-qt4-autotools] $ /bin/sh -xe /tmp/hudson1608683673271057782.sh
+ IMAGE=lyxproject/build-lyx-using-ubuntu-xenial-qt4-autotools
+ C_BUILD=/build
+ C_WS=/build/workspace
+ C_SCRIPT=/build/build_lyx.sh
+ docker run --rm -v 
:/build/workspace
 lyxproject/build-lyx-using-ubuntu-xenial-qt4-autotools /build/build_lyx.sh 
/build/workspace
./autogen.sh: 11: ./autogen.sh: automake (GNU automake) 1.15: not found
LyX requires automake >= 1.14
Build step 'Execute shell' marked build as failure

Re: Fix for vertical table border for added column

[racoon]

On 21.08.2017 22:31, Jean-Marc Lasgouttes wrote:

Le 21/08/2017 à 14:54, racoon a écrit :
I manually applied the second patch now. There was a missing line in 
your patch ...

    -    // fall through


Sorry for the inconvenience. I don't know how the comment got missing.


The was changed recently by Juergen. You should update your tree 
(equivalent to a "git pull") and your commit will be updated against the 
latest master (if everything goes right :).


Thanks! I did a "git pull -- rebase" on the master. But it seems neither 
to affect the branch I created for the table fixes, nor the patches I 
create relative to master.


When I do a "git pull" on my branch I get the following message:

"There is no tracking information for the current branch.
Please specify which branch you want to rebase against.
See git-pull(1) for details.

git pull  

If you wish to set tracking information for this branch you can do so with:

git branch --set-upstream-to=origin/ SomeTableFixes"

So what is the right command here?

Daniel

Re: listing file without extension

[Paul A. Rubin]

On 08/21/2017 04:59 PM, Dr Eberhard Lisse wrote:

Hi,

would it be unexpected that an included listing file without extension,
ie something like

  filename

would throw an error that filename.tex is not found?


el

Does this happen if you specify a period (but no extension) at the end 
of the file name?


Paul

Re: 404 on manuals on lyx.org

[Tommaso Cucinotta]

On 21/08/2017 23:09, Christian Ridderström wrote:

- The link texts could be LyX vs PDF instead of EN/FR etc.


tried also to play with the clikkable PDF/LyX icons that bring you to the file, 
but if we get tens of those I expect the page to become difficult to browse.


I added example of how you can use an image as the "link text".
Also how it can be resized. But it's better if the uploaded image has
the proper size from the beginning.


+1, thanks.

I checked that, with the converted manuals from the generate_manuals_for_web.sh 
script, we have:

-) 4 langs with complete 5 manuals on the page (Intro, Tutorial, UserGuide, 
Math, Customization, EmbeddedObjects).
-) 22 langs with the Intro (18 besides the 4 complete langs)
-) 18 langs with the Tutorial (14 besides the 4 complete langs)
-) 17 langs with both Intro and Tutorial

But who knows how many of these are actually maintained and updated to what LyX 
release ?

So, I was wondering whether it was worth to go for:
-) growing the current table to a maxi table (22 langs x 5 manuals) with all 
possible intersections (likely different tables for different doc types)
-) adding to the current table a new one, pointing only to the Intro & Tutorial 
of the 22 langs having at least one of them.

Both would have to be auto-generated of course.

Thoughts ?

T.

Re: listing file without extension

[Richard Heck]

On 08/21/2017 04:59 PM, Dr Eberhard Lisse wrote:
> Hi,
>
> would it be unexpected that an included listing file without extension,
> ie something like
>
>  filename
>
> would throw an error that filename.tex is not found?

It's not surprising, in a way: I'm guessing that, seeing no extension,
LaTeX looks for a TeX file. But it's probably also true that LyX should
do something here, if possible.

But others will know more. I don't use listings

Richard

Re: Tip: Use shellcheck to do static analysis of sh and bash scripts

[Richard Heck]

On 08/20/2017 12:32 PM, Christian Ridderström wrote:
> Hi,
>
> Just sharing a tip for when you write sh or bash scripts. Use a static
> analysis tool like 'shellcheck' on the scripts.
> https://www.shellcheck.net/

Thanks for the reference. It's a useful tool.

> Below is a list of LyX scripts for which the shellcheck indicates at
> least something:
>
> HEAD @ chrid-mb $ find . -name "*.sh" -exec bash -c 'shellcheck "$1" >
> /dev/null || echo "Issue found with: $1"; ' "" {} \;
> Issue found with: ./3rdparty/boost/extract.sh

Not ours.

> Issue found with: ./autogen.sh

I fixed two very minor issues with that one and one weird one I did not
even know about.
See here: https://github.com/koalaman/shellcheck/wiki/SC2015.

> Issue found with: ./development/attic/rename.sh

Attic.

> Issue found with: ./development/autotests/export-in.sh
> Issue found with: ./development/autotests/run-tests.sh
> Issue found with: ./development/autotests/single-test.sh
> Issue found with: ./development/keystest/add_write_perms.sh
> Issue found with: ./development/keystest/cache-bisect.sh
> Issue found with: ./development/keystest/doNtimes.sh
> Issue found with: ./development/keystest/killtest.sh
> Issue found with: ./development/keystest/killtestpy.sh
> Issue found with: ./development/keystest/list_all_children.sh
> Issue found with: ./development/keystest/lyx_make.sh
> Issue found with: ./development/keystest/main.sh
> Issue found with: ./development/keystest/make_screen_shots.sh
> Issue found with: ./development/keystest/maketar.sh
> Issue found with: ./development/keystest/report.sh
> Issue found with: ./development/keystest/report_html.sh
> Issue found with: ./development/keystest/reproduce.sh
> Issue found with: ./development/keystest/setup.sh
> Issue found with: ./development/keystest/shared_functions.sh
> Issue found with: ./development/keystest/shared_variables.sh
> Issue found with: ./development/keystest/watch_keytest.sh

Someone who deals with the tests might look at these.

> Issue found with: ./development/tools/count_lines_of_included_code.sh
> Issue found with:
> ./development/tools/count_total_lines_of_compiled_code.sh
> Issue found with: ./development/tools/header_check.sh
> Issue found with: ./development/tools/list_included_headers.sh

All pretty old. I'm not sure if anyone even uses them.

> Issue found with: ./development/tools/separator-convert.sh

Moved to attic. Was for 2.2.->2.3 document conversion.

> Issue found with: ./development/tools/update-po.sh
> Issue found with: ./development/tools/updatelfuns.sh
> Issue found with: ./development/tools/updatestats.sh

Fixed all found issues with these.

Also examined the lyx-build script and put some comments into it.

Richard

Re: 404 on manuals on lyx.org

[Tommaso Cucinotta]

On 21/08/2017 17:02, Pavel Sanda wrote:

https://wiki.lyx.org/uploads/


or from within wiki:
uploads:/path/file.png


solved, I was using "uploads:path/to/..." instead of "uploads:/path/to/..."

A minor issue I'm seeing is that, clicking on a tutorial .lyx file in any 
language, Firefox proposes me to open the file with LyX, whilst clicking on any 
other .lyx document (not a tutorial), Firefox opens its text content in the 
webpage. Some misconfiguration of MIME types on the server ?

Thanks,

T.

Re: 404 on manuals on lyx.org

[Christian Ridderström]

Tommaso Cucinotta  writes:

> On 20/08/2017 20:20, Christian Ridderström wrote:
>> - Perhaps write out English, Español etc in the headings
>
> I made an attempt to rotate the text, to keep the table compact, via
> CSS attributes, but the rotated one didn't show well, because it was
> rotating the cell borders as well :(. Perhaps a hack might be to keep
> the heading cell as a perfect square ;-P.

I tested making the header text smaller, have a look at the playground
page now. Looks ok to me, but maybe you think it's still to wide?

>> - The link texts could be LyX vs PDF instead of EN/FR etc.
>
> tried to upload a .pdf icon from LyX, I've put it here:

> Now, how can I get that image to show up in the wiki ? What is the URL
> it becomes visible as ? I tried to follow pmwiki's (upload:, attach:),
> but didn't work.

Seems like you've solved it now.

I added example of how you can use an image as the "link text".
Also how it can be resized. But it's better if the uploaded image has
the proper size from the beginning.

/Christian

listing file without extension

[Dr Eberhard Lisse]

Hi,

would it be unexpected that an included listing file without extension,
ie something like

 filename

would throw an error that filename.tex is not found?


el

Re: numbers/ids of posts on mail-archive.com vs. gmane.org?

[Christian Ridderström]

Scott Kostyshak  writes:

> On Mon, Aug 07, 2017 at 11:49:19AM +0200, Pavel Sanda wrote:
>> Scott Kostyshak wrote:
>> > When I'm reading email in mutt, all I do is press a shortcut (I use [ma for
>> > "mail archive"), and it copies the above link to my clipboard so I can 
>> > paste
>> > it in my email (or on trac). If anyone is using mutt, let met know if you
>> > want the script.
>> 
>> Nice hack, I'll be interested to see it. P
>
> Let me clean up the hack to make it a little less hackish. I've been meaning 
> to
> clean it up so this will be a good opportunity.

In case there's anyone else using Gnus, and if I need it in the future,
below is a function I just wrote to copy the message ID.

If I execute the function in a message buffer it will find the
message-ID and copy it into the "kill ring", so I can later e.g. "yank" it
into a message I'm composing.

(defun copy-message-ID ( arg)
  "Copy Message-ID field.
This command must be executed in a gnus message buffer."
  (interactive)
  (save-excursion
(beginning-of-buffer)
(gnus-summary-toggle-header 1)
(search-forward-regexp "^Message-ID: ")
(let ((beg-of-ID (point)))
  (end-of-line)
  (kill-ring-save beg-of-ID (point)))
(gnus-summary-toggle-header -1)
)
  )

/Christian

PS
Caveat: It's a long time since I wrote lisp so the function might not be
very robust etc.

Re: #8908: Instant preview does not work if package `minted` is used

[Allan Leal]

Sorry for not responding earlier. LyX works just great with minted since 
version 2.2 (maybe even 2.1).



On 21/08/17 07:45, LyX Ticket Tracker wrote:

#8908: Instant preview does not work if package `minted` is used
---+-
  Reporter:  allanmulin |   Owner:  lasgouttes
  Type:  defect |  Status:  new
  Priority:  normal |   Milestone:
Component:  preview-latex  | Version:  2.0.6
  Severity:  normal |  Resolution:
  Keywords: |
---+-

Comment (by skostysh):

  allanmulin, are you still around? If so, it would be great if you could
  test 2.3.0beta1, which has native minted support. You can download
  installers [ftp://ftp.lyx.org/pub/lyx/devel/lyx-2.3/2.3.0-latest here].

Re: How to access the list efficiently? Re: Long threads? / list etiquette?

[Christian Ridderström]

Guenter Milde  writes:

> On 2017-08-21, Pavel Sanda wrote:
>> Christian Ridderström wrote:
>>> * But then I stumbled upon a still running news service for the lists.
>>>   Possibly this is related to the old 'gmane' service. E.g.
>
>>> nntp+news.gwene.org:gmane.editors.lyx.devel
>
>>> The 'news' interface is working well so far. And I can go back and see
>>> posts from something like 2003 or so.
>
>> I added the link above to our email lists page.
>
> Also the "traditional" GMANE news interface works fine with lyx. I use it
> with the slrn news reader:
>
>   slrn -n -h news.gmane.org

Thanks Günter. I've now switched my Gnus to use 'news.gmane.org' instead
of 'news.gwene.org' and it seems to work fine.

I've therefore also updated the wiki page to refer to 'news.gmane.org'.

/Christian

The updated note:

-> '''Note:''' As of 14 September 2016, the GMANE web interface is being
   rebuilt following a transfer of ownership. Unfortunately access to
   the LyX mailing lists through the GMANE web interface is still (Aug
   2017) not working.  However, the 'news' service is still operational
   and you can use a news reader to e.g. access posts in the developer's
   list through

--> @@nntp+news.gmane.org:gmane.editors.lyx.devel@@.

Re: numbers/ids of posts on mail-archive.com vs. gmane.org?

[Christian Ridderström]

Christian Ridderström  writes:

> Hi,
>
> The wiki has "InterLinks", which is simply a convenient way to refer
> to certain web pages.  For instance, this markup
>
> bug:10481
>
> is automatically converted into this link
> http://www.lyx.org/trac/ticket/10481.
>
> Similarly, there's prefixes like LyxDevelPost and LyxUsersPost which
> were used to refer to gmane.org. Unfortunately gmane.org doesn't seem
> to contain the LyX lists anymore :-(
>
> I just now tested repointing the prefix "LyxDevelPost" from gmane.org
> to mail-archive.com, so e.g.this currently works: LyxDevelPost:200333
>
> There's a problem though... it seems the IDs of posts, i.e. the
> number, is different for gmane.org versus mail-archive.com. My
> repointing would therefore mean that a pre-existing link into
> gmane.org "evolved" from initially working fine, to not working at
> all, to suddenly pointing to the wrong post in
> mail-archive.com. *sigh*

An update in case someone stumbles on this thread in the future.

As a news service, 'gmane' is still around. It's the web interface
that's not working. In another thread Günter wrote:

… the "traditional" GMANE news interface works fine with lyx. I
use it with the slrn news reader:

  slrn -n -h news.gmane.org

Separately I accidentally found that the news interface also works
through 'news.gwene.org', e.g. as:

nntp+news.gwene.org:gmane.editors.lyx.devel

/Christian

Re: 404 on manuals on lyx.org

[Pavel Sanda]

Pavel Sanda wrote:
> Tommaso Cucinotta wrote:
> > Now, how can I get that image to show up in the wiki ? What is the URL it 
> > becomes visible as ? I tried to follow pmwiki's (upload:, attach:), but 
> > didn't work.
> 
> https://wiki.lyx.org/uploads/

or from within wiki:
uploads:/path/file.png

p

Re: 404 on manuals on lyx.org

[Pavel Sanda]

Tommaso Cucinotta wrote:
> Now, how can I get that image to show up in the wiki ? What is the URL it 
> becomes visible as ? I tried to follow pmwiki's (upload:, attach:), but 
> didn't work.

https://wiki.lyx.org/uploads/

Pavel

Re: Fix for vertical table border for added column

[Kornel Benko]

Am Montag, 21. August 2017 um 22:24:10, schrieb racoon 
> > Playing with the new settings now ...
> > It is somehow requiring getting used to ... but I like it.
> 
> I am not sure I follow. What "new settings"?
> 
> Daniel

I am able to set arbitrary borders with the table toolbar, but
with the tabular settings dialog it is often not possible. 

Kornel

signature.asc
Description: This is a digitally signed message part.

Re: Require C++11 for 2.3?

[Stephan Witt]

Am 20.08.2017 um 15:33 schrieb Christian Ridderström :
> 
> Stephan Witt  writes:
> 
>> Am 16.08.2017 um 10:47 schrieb Jean-Marc Lasgouttes :
>>> Le 16 août 2017 02:51:44 GMT+02:00, c...@lyx.org a écrit :
>>> 
 Did this happen, i.e. requiring C++11?
 /Christian
>>> 
>>> We require something close enough to c++11, the minimum being GCC
>>> 4.6. For 2.4, we'll require a real c++11.
> 
> So no (I was really only checking [*]).
> 
>> What does this statement mean for Apple Mac clang compiler?
>> 
>> I remember we had problems with thread_local on Mac…
>> 
>> What does this mean for the minimum supported OS version?
>> 
>> Perhaps one can provide a minimal hello-world example with
>> all c++11 features we require for a real usable compiler
>> and run-time, please?
> 
> Are you saying there might be a problem compiling LyX on an older
> version of macOS?
> 
> This page
>  https://trac.macports.org/wiki/XcodeVersionInfo
> can be useful to map Xcode release to clang release.
> 
> According to this page
>  http://clang.llvm.org/cxx_status.html
> the Clang 3.3 release fully supports C++11.
> 
> If I read the pages correctly, as of Xcode 5.1 the Apple clang is
> based on LLVM 3.4svn and should thus fully support C++11.
> Xcode 5.1 is available for OS X 10.8, but seemingly not for OS X 10.7.
> 
> However, the above is (I think) only for the compiler. The C++ library
> that's used also needs to fully support C++11.
> 
> Not sure how to check that easily. The following post (in the update) seem to
> indicate that C++11 is supported as of macOS X 10.9. I could be reading
> to much into the post though.

ATM I’m building LyX on two systems: with Xcode 8.2.1 on macOS 10.11.6 for 
systems
running at least macOS 10.7 and on macOS 10.8.6 for systems with macOS 10.6 at 
least.

I agree the most important is the runtime-library equipment of the macOS where 
LyX
should be run on. E.g. the change to avoid deprecation warnings would cause a 
minimum
OS version of 10.10. Unfortunately we don’t know if there are users of LyX with
elder systems (except of JMarc with 10.7 :)

Regarding the C++11 status of Apple clang I’m not sure if the version number is
enough to be sure it works. See the post about thread_local here:

http://stackoverflow.com/questions/28094794/why-does-apple-clang-disallow-c11-thread-local-when-official-clang-supports

That’s really problematic, when I try to install some macport packages they
depend on the llvm-3.5 of macports already. That’s a bit weird on a system
with an llvm based clang as standard compiler.

I have to admit I’m not sure how the current state of clang on mac is, though.

Stephan 

Re: 404 on manuals on lyx.org

[Tommaso Cucinotta]

On 20/08/2017 20:20, Christian Ridderström wrote:

- Perhaps write out English, Español etc in the headings


I made an attempt to rotate the text, to keep the table compact, via CSS 
attributes, but the rotated one didn't show well, because it was rotating the 
cell borders as well :(. Perhaps a hack might be to keep the heading cell as a 
perfect square ;-P.


- The link texts could be LyX vs PDF instead of EN/FR etc.


tried to upload a .pdf icon from LyX, I've put it here:

ftp wiki.lyx.org
Connected to www.lyx.org.
220 Welcome to the LyX wiki FTP service.
Name (wiki.lyx.org:tommaso): lyxftp
331 Please specify the password.
Password:
230 Login successful.

cd LyX
cd Manuals
put buffer-export_pdf.png
dir
-rw-r--r--1 ftp  ftp  8170 Aug 21 12:46 buffer-export_pdf.png

Now, how can I get that image to show up in the wiki ? What is the URL it 
becomes visible as ? I tried to follow pmwiki's (upload:, attach:), but didn't 
work.


Do you mean how to make an image appear on a wiki page
(http://www.pmwiki.org/wiki/PmWiki/Images) or how to upload an image
onto the server?


seemingly the upload part is ok, I just can't make it visible from a wiki page 
now.


General tip: Test things in the group "/Test", e.g. see here
 http://wiki.lyx.org/Test/Images


that's exactly what I was trying to follow :(


Or use a playground page, e.g. http://wiki.lyx.org/Playground/AngusWikiSandbox


moved Manuals2 to

  http://wiki.lyx.org/Playground/ManualsPG

(feel free to edit, if you can let any image appear there, we're done!)

Thx,

T.

Re: Fix for vertical table border for added column

[Jean-Marc Lasgouttes]

Le 21/08/2017 à 14:54, racoon a écrit :
I manually applied the second patch now. There was a missing line in 
your patch ...

-// fall through


Sorry for the inconvenience. I don't know how the comment got missing.


The was changed recently by Juergen. You should update your tree 
(equivalent to a "git pull") and your commit will be updated against the 
latest master (if everything goes right :).


JMarc

Re: Fix for vertical table border for added column

[racoon]

On 20.08.2017 20:17, Kornel Benko wrote:

Am Sonntag, 20. August 2017 um 16:20:15, schrieb racoon 

On 20.08.2017 04:13, Jean-Marc Lasgouttes wrote:

Le 19/08/2017 à 20:30, Kornel Benko a écrit :

Am Samstag, 19. August 2017 um 19:52:18, schrieb Jean-Marc Lasgouttes


Le 19 août 2017 19:44:01 GMT+02:00, Kornel Benko  a
écrit :

I prefer to wait for a new patch.


Did you apply the 0001 patch first?

JMarc


With 0001 or without, the patch 0002 fails.


Indeed, I just got access to a real computer and came to the same
conclusion.


Thanks. Okay, so the first patch works. That's great since it is the one
I suggest for 2.3.0.


Sorry, I did not say that the first patch works. Only that it applied to the 
sources.


On the second patch: I am not sure what went wrong. And the .rej file
does not tell me much about that either. I created a new patch but it is
just the same. Not sure what to do from here.


How did you create the patch?


I used Tortoise Git: Right click on the main folder and "Create Patch 
Serial...".



# git diff src/insets/InsetTabular.cpp >

should be OK.


Maybe I should try to use bash in the future.


I manually applied the second patch now. There was a missing line in your patch 
...
-   // fall through


Sorry for the inconvenience. I don't know how the comment got missing.


Playing with the new settings now ...
It is somehow requiring getting used to ... but I like it.


I am not sure I follow. What "new settings"?

Daniel

Re: Changes to git branches, regarding 2.3.0 development

[Christian Ridderström]

Scott Kostyshak  writes:

> On Sun, Aug 20, 2017 at 03:45:11PM +0200, Christian Ridderström wrote:
>
>> FYI, the CI jobs are testing branch 'master', so as it is we don't have
>> automatic testing of changes to branch '2.3.x'.
>
> OK thanks for the warning.

It should be possible to make a CI job operate on multiple branches, but
there's *ahem* apparently a risk of triggering a lot of jobs that way.

So if someone wants a CI job for 2.3.x, it might be easier to simply
duplicate one of the existing jobs.

/Christian

Re: Question for Guillaume about b30f8d3c and GuiFontMetrics::countExpanders

[Jean-Marc Lasgouttes]

Le 27/07/2017 à 16:11, Guillaume MM a écrit :

The reasoning was that how many expanders there are in a string is
toolkit-specific. This implementation was by testing and reading the
docs and source code of Qt, and does not correspond to my knowledge to
any Unicode standard (say). So, using the frontends/ virtual interface
is more appropriate, and virtual functions cannot be non-member nor
static. Concretely, the FontMetrics object is used to know which
frontend one refers to.


Thanks for the clarification, Guillaume.

JMarc

Re: Require C++11 for 2.3?

[Jean-Marc Lasgouttes]

Le 20/08/2017 à 15:33, Christian Ridderström a écrit :

What does this mean for the minimum supported OS version?

Perhaps one can provide a minimal hello-world example with
all c++11 features we require for a real usable compiler
and run-time, please?


Yes, we could improve the C++ compiler test of configure to do this.
Currently, autoconf uses:

   template 
   struct check
   {
   static_assert(sizeof(int) <= sizeof(T), "not big enough");
   };

   typedef check right_angle_brackets;

   class TestDeleted
   {
   public:
   TestDeleted() = delete;
   };


   int a;
   decltype(a) b;

   typedef check check_type;
   check_type c;
   check_type&& cr = static_cast(c);

   auto d = a;

If I read the pages correctly, as of Xcode 5.1 the Apple clang is
based on LLVM 3.4svn and should thus fully support C++11.
Xcode 5.1 is available for OS X 10.8, but seemingly not for OS X 10.7.


Yes, my understanding is that 10.7 is not possible anymore out of the 
box. Note that it is possible to install a newer version of gcc or clang 
there and maybe compile LyX. Unfortunately (and unsurprisingly), my 10.7 
box is in a too bad shape to be a pleasant development box.


JMarc

Re: CI job generating PDFs? Was: 404 on manuals on lyx.org

[Guenter Milde]

On 2017-08-20, Christian Ridderström wrote:
> Guenter Milde  writes:
>> On 2017-08-11, Christian Ridderström wrote:
>>> On 11 August 2017 at 13:03, Pavel Sanda  wrote:
 Christian Ridderström wrote:

 > [*] It might make sense to have a CI job that builds PDFs etc from the
 > manuals as a separate test.

...

> Some months ago I created a CI job that runs (some of?) the tests.

...

> Due to the many tests failing it didn't seem so useful to deploy.
> Here's the (presumably) relevant line from the log:

> 68% tests passed, 2073 tests failed out of 6522

This warrants a look into the test setup, but may be no problem if the very
small subset of tests exporting documentation to the default output format
works fine. However,

...

> From there I then navigated to e.g.

> 
> https://ci.inria.fr/lyx/job/testing-Jenkins/job/ctest/ws/build/autotests/out-home/sv/splash_defaultF.pdf3

> I was able to download that file and view it, although my mac required
> me (!!!???) to first rename the extension from .pdf3 to .pdf, even when
> I tried to launch 'Preview' on the file from the command line.

We would need to:

* select the *.pdf2 (PDF(pdflatex) files matching the manuals and rename
  them to *.pdf

* select required graphic files

* move them into a sensible directory hierarchy

All in all, it seems simpler to keep the documentation generation as a
separate task.


Günter

Re: How to access the list efficiently? Re: Long threads? / list etiquette?

[Guenter Milde]

On 2017-08-21, Pavel Sanda wrote:
> Christian Ridderström wrote:
>> * But then I stumbled upon a still running news service for the lists.
>>   Possibly this is related to the old 'gmane' service. E.g.

>>  nntp+news.gwene.org:gmane.editors.lyx.devel

>> The 'news' interface is working well so far. And I can go back and see
>> posts from something like 2003 or so.

> I added the link above to our email lists page.

Also the "traditional" GMANE news interface works fine with lyx. I use it
with the slrn news reader:

  slrn -n -h news.gmane.org

Günter

Re: [LyX/master] oops, git is playing games with me.

[Pavel Sanda]

Christian Ridderström wrote:
> There's an FTP on the LyX server... I sent out details earlier today.
> So perhaps 'sshfs' is an option for uploading things.

Maybe we could have separate account just for manuals and possibility to
directly link to that folder from web/wiki. That way Tommaso can directly
upload his exports to web without relying on me. That would be good.

> - From where are the files uploaded? A developer's computer? A CI job?

>From local machine where someone runs the committed script for building 
>manuals.

> - Are uploads to be triggered automatically?

Unlikely.

> - How often would we do new uploads? Once per release, a few times per 
> release?

At most once per release, maybe even once per major relase.

> - To where should the files be uploaded?

Internally does not matter, we just need bash-like access for rm/cp -r  commands
(ftp through curl-ftps is just fine for that) and ability to directly link
it through URL.

> As I wrote in some other post I also thinks it's good to have a separate
> staging area for review, and a separate deployment area to which users
> are referred.

I do not see that we have enough manpower to manage such complications. At this
moment, even after one decade, we were not able to publish in html form 
*anything*.
So keep it as simple as possible...

Pavel

Re: How to access the list efficiently? Re: Long threads? / list etiquette?

[Pavel Sanda]

Christian Ridderström wrote:
> * But then I stumbled upon a still running news service for the lists.
>   Possibly this is related to the old 'gmane' service. E.g.
> 
>   nntp+news.gwene.org:gmane.editors.lyx.devel
> 
> The 'news' interface is working well so far. And I can go back and see
> posts from something like 2003 or so.

I added the link above to our email lists page.

Pavel