Re: `make all` too verbose after merge #84

2020-08-05 Thread Han-Wen Nienhuys
On Wed, Aug 5, 2020 at 6:28 PM Werner LEMBERG wrote: > > > You haven't yet confirmed that if you 'remove/uninstall' > > extractpdfmark you do NOT get the messages, only that you have it > > installed and you get them - which is expected. > > Sorry for being imprecise. I have *always* `extractpdf

Re: `make all` too verbose after merge #84

2020-08-05 Thread Werner LEMBERG
> You haven't yet confirmed that if you 'remove/uninstall' > extractpdfmark you do NOT get the messages, only that you have it > installed and you get them - which is expected. Sorry for being imprecise. I have *always* `extractpdfmark` installed, and since a long time (a few months) I *never*

Re: `make all` too verbose after merge #84

2020-08-05 Thread pkx166h
On 05/08/2020 15:00, Werner LEMBERG wrote: extractpdfmark not tex (I assume that comment was a typo?) Yes. anyway with it installed you will get those messages, without you won't (or at least I did not). and it has been a thing for me for a lot longer than 3 weeks. Well, as reported, I di

Re: `make all` too verbose after merge #84

2020-08-05 Thread Werner LEMBERG
> extractpdfmark not tex > > (I assume that comment was a typo?) Yes. > anyway with it installed you will get those messages, without you > won't (or at least I did not). > > and it has been a thing for me for a lot longer than 3 weeks. Well, as reported, I didn't get those page messages sin

Re: `make all` too verbose after merge #84

2020-08-05 Thread James
Werner On 05/08/2020 12:35, Werner LEMBERG wrote: Nope, IIRC. Only warnings that 'font foo is too large to be included as a subfont' or something similar. I've just tried to compile 2.20 and I get those same Page xx message back then. Hmm. Go check out b39b2e652 for instance (that is the 2.

Re: `make all` too verbose after merge #84

2020-08-05 Thread Werner LEMBERG
>> Nope, IIRC. Only warnings that 'font foo is too large to be included >> as a subfont' or something similar. > > I've just tried to compile 2.20 and I get those same Page xx message > back then. Hmm. > Go check out b39b2e652 for instance (that is the 2.20 'bump welcome' > commit that Phil do

Re: `make all` too verbose after merge #84

2020-08-05 Thread James
Hello On 05/08/2020 11:01, Federico Bruni wrote: On Wed, 5 Aug, 2020 at 07:53, James wrote: I am pretty sure I have been seeing these page counts for a while. Me too. I think it happens when you have extractpdfmark installed. yes that is correct - I remember now. You can uninstall it if y

Re: `make all` too verbose after merge #84

2020-08-05 Thread Federico Bruni
On Wed, 5 Aug, 2020 at 07:53, James wrote: I am pretty sure I have been seeing these page counts for a while. Me too. I think it happens when you have extractpdfmark installed.

Re: `make all` too verbose after merge #84

2020-08-05 Thread pkx166h
Hello Werner, On 05/08/2020 09:39, Werner LEMBERG wrote: On 05/08/2020 04:37, Werner LEMBERG wrote: If I now execute `make doc -j4`, I get zillions lines Page 53 Page 1 Page 2 Page 235 ... emitted by gs, and which are completely useless and clutter the terminal output. I

Re: `make all` too verbose after merge #84

2020-08-05 Thread Werner LEMBERG
> On 05/08/2020 04:37, Werner LEMBERG wrote: >> If I now execute `make doc -j4`, I get zillions lines >> >>Page 53 >>Page 1 >>Page 2 >>Page 235 >>... >> >> emitted by gs, and which are completely useless and clutter the >> terminal output. I let the above command run overnigh

Re: `make all` too verbose after merge #84

2020-08-04 Thread James
Werner On 05/08/2020 04:37, Werner LEMBERG wrote: If I now execute `make doc -j4`, I get zillions lines Page 53 Page 1 Page 2 Page 235 ... emitted by gs, and which are completely useless and clutter the terminal output. I let the above command run overnight so that I can check

`make all` too verbose after merge #84

2020-08-04 Thread Werner LEMBERG
If I now execute `make doc -j4`, I get zillions lines Page 53 Page 1 Page 2 Page 235 ... emitted by gs, and which are completely useless and clutter the terminal output. I let the above command run overnight so that I can check it in the morning; however, inspite of having a really l