> I normally just use .FG to title my code listings.
But in such case you need to modify the "Lifg" dynamically.
What is more, you increase the register 'Fg' counter on listings.
And what about the list of figures?
Does it become list of figures and listings?
Best reg
.
Best regards,
Michał Kruszewski
Sent with ProtonMail Secure Email.
‐‐‐ Original Message ‐‐‐
On Tuesday, May 11, 2021 1:10 PM, Damian McGuckin wrote:
> On Tue, 11 May 2021, Micha? Kruszewski wrote:
>
> > > I normally just use .FG to title my code listings.
> >
>
PR on the GitHub/GitLab it
would probably be much more popular.
Best regards,
Michał Kruszewski
Sent with ProtonMail Secure Email.
‐‐‐ Original Message ‐‐‐
On Monday, May 17, 2021 11:30 PM, Jeff Conrad wrote:
> On Monday, May 17, 2021 1:05 PM, James K. Lowden wrote
>
> > Does
Thanks!
The trick with TP macro works.
Best regards,
Michał Kruszewski
Sent with ProtonMail Secure Email.
‐‐‐ Original Message ‐‐‐
On Monday, May 17, 2021 10:26 PM, Tadziu Hoffmann
wrote:
> > Does anyone how to decrease the top margin with mm macros?
> > There is VM m
format in the repository.
I have checked both PAGE=A4 and PAGE=letter and it looks like there is no
difference.
Best regards,
Michał Kruszewski
Sent with Proton Mail secure email.
--- Original Message ---
On Tuesday, April 4th, 2023 at 3:15 PM, G. Branden Robinson
wrote:
> Hi Mic
file) and I will easily
generate ToC with Perl/Python script and Makefile target.
I guess it is currently not possible?
2. PDF meta data.
pdfroff has .pdfinfo, how to achieve the same with groff?
Best regards,
Michał Kruszewski
Sent with Proton Mail secure email.
--- Original Message -
was achieved is not so easy as it looks
like there is quite a lot *nix wizardry behind it.
Best regards,
Michał Kruszewski
Sent with Proton Mail secure email.
--- Original Message ---
On Tuesday, April 4th, 2023 at 6:58 PM, G. Branden Robinson
wrote:
> At 2023-04-04T16:26:30+0
ess is generated.
I am attaching my "favorite" output so far.
Best regards,
Michał Kruszewski
Sent with Proton Mail secure email.
--- Original Message ---
On Wednesday, April 5th, 2023 at 3:19 PM, G. Branden Robinson
wrote:
> Hi Michał,
>
> At 2023-04-05T08:25:28+000
or vertical space.
I am attaching a little reproducer.
Compile with groff 1.22.4 and groff 1.23.0rc3.
You will easily see the changes in the generated layout.
Best regards,
Michał Kruszewski
Sent with Proton Mail secure email.
--- Original Message ---
On Wednesday, April 5th, 2023 at 6:06 PM
go.
Nevertheless, I admire your mom work.
You have probably invested hundreds or maybe even thousand of hours into it.
Best regards,
Michał Kruszewski
Sent with Proton Mail secure email.
--- Original Message ---
On Wednesday, April 5th, 2023 at 7:09 PM, Peter Schaffter
wrote
So it is now explained why .bp is broken.
I am attaching yet another reproducer.
This time there is a problem with the .sp before Abstract.
In 1.23.0.rc3 this .sp is simply ignored, while in 1.22.4 it is correctly
applied.
Best regards,
Michał Kruszewski
Sent with Proton Mail secure email
it
in groff; the order in time doesn't matter. The FSF want 100%
ownership to enforce copyright but deny 100% ownership of that
earlier work in doing so.
I do not get this.
Can you elaborate or provide an example?
Best regards,
Michał Kruszewski
Sent with Proton Mail secure emai
I do not believe it works this way.
It would be extremely stupid.
I can image this applies when you copy large amount of code, but single 25
lines function?
No one would contribute to GNU projects if it worked like this.
Best regards,
Michał Kruszewski
Sent with Proton Mail secure email
By patches you mean `git diff` output?
Best regards,
Michał Kruszewski
Sent with Proton Mail secure email.
--- Original Message ---
On Saturday, June 3rd, 2023 at 4:47 PM, G. Branden Robinson
wrote:
> Hi Michał,
>
> (Please let me know if you're prefer not to be C
of my papers include images, so I use -U
almost all the time.
Best regards,
Michał Kruszewski
Sent with Proton Mail secure email.
--- Original Message ---
On Sunday, July 30th, 2023 at 12:26 PM, G. Branden Robinson
wrote:
> Hi Michał,
>
> At 2023-07-30T08:29:35+000
macros uppercase and some lowercase?
How do I know where to look for all PDF macros documentation?
Best regards,
Michał Kruszewski
Sent with [Proton Mail](https://proton.me/) secure email.
the text inside the frame or changing the color of nothing.
Does anyone know how to easily change the color of the background in the box or
the color of the box frame?
Best regards,
Michał Kruszewski
Sent with [Proton Mail](https://proton.me/) secure email.
ot;LS" or
"LST".
Best regards,
Michał Kruszewski
Sent with [ProtonMail](https://protonmail.com) Secure Email.
ut the top margin always has the same size.
Looks like the top margin can only be increased.
Unfortunately, one can not control the top margin with PGFORM macro.
Best regards,
Michał Kruszewski
Sent with [ProtonMail](https://protonmail.com) Secure Email.
''%''. It no longer works.
Are all of the above conscious changes?
If they are, how can I bring back what I had in 1.22.4 using 1.23.0.rc3?
I have skimmed the changelog, but to be honest i do not feel it is useful in my
case.
Best regards,
Michał Kruszewski
Sent with [Proton Mail](https://proton.me/) secure email.
Hi Branden,
I have tried 1.23.0rc4 and it still has backward compatibility issues with .sp
and .bp I have described some time ago.
Is it intended?
Best regards,
Michał Kruszewski
Sent with [Proton Mail](https://proton.me/) secure email.
Is there any tutorial on how to contribute to the groff?
The https://www.gnu.org/software/groff/ website is rather modest in this term.
Where do I need to register?
How to prepare pull requests?
Best regards,
Michał Kruszewski
Sent with [Proton Mail](https://proton.me/) secure email.
is correct).
Best regards,
Michał Kruszewski
Sent with [Proton Mail](https://proton.me/) secure email.
Why does PDFPIC require unsafe mode -U, but PSPIC doesn't?
If I understand correctly one can easily execute shell commands from PostScript.
Best regards,
Michał Kruszewski
Sent with [Proton Mail](https://proton.me/) secure email.
24 matches
Mail list logo