#groff — Public Fediverse posts

I don't like #AI. I think it's problematic in a lot of ways, that I won't repeat here as I believe you heard these (very much true) arguments 100 times.

But #DuckAI helped me quite a lot yesterday, and I don't know how to feel about that. By curiosity, I made it write #elisp code to create new useful commands for #emacs which will help me in my everyday work (for example `C-c m` now creates a PDF using `pdfmom -k` so I don't have to use a terminal at the same time when I use #groff, `C-c t` adds `/|` before some punctuations signs following French typographic rules, …). These functions are very simple, most of you here could have written them by hand in less time than it took me to write the prompts, but I'm no developer, and don't have the time to become one, unfortunately. They work as intended (I can control that as, again, they're simple things), and I more or less understand them, as the #LLM described them. I even asked it questions to understand some parts of the code, and it answered (correctly it seems; I checked and as far as I can know, its answers seem legit), so I was able to modify them by hand to fine-tune them. One was wrong, but when I sent it the error message, it corrected it and explained the error to me.

It didn't feel like I was relinquishing brain power; in the contrary I learnt things. I could have done that by hand, and I would have learnt far more, but it would have taken months and I don't have months: a bird in the hand is worth two in the bush.

I still think that LLMs are a problem for our societies, but even more so than I thought as it seems to be actually useful in some cases.

I don't like #AI. I think it's problematic in a lot of ways, that I won't repeat here as I believe you heard these (very much true) arguments 100 times.

But #DuckAI helped me quite a lot yesterday, and I don't know how to feel about that. By curiosity, I made it write #elisp code to create new useful commands for #emacs which will help me in my everyday work (for example `C-c m` now creates a PDF using `pdfmom -k` so I don't have to use a terminal at the same time when I use #groff, `C-c t` adds `/|` before some punctuations signs following French typographic rules, …). These functions are very simple, most of you here could have written them by hand in less time than it took me to write the prompts, but I'm no developer, and don't have the time to become one, unfortunately. They work as intended (I can control that as, again, they're simple things), and I more or less understand them, as the #LLM described them. I even asked it questions to understand some parts of the code, and it answered (correctly it seems; I checked and as far as I can know, its answers seem legit), so I was able to modify them by hand to fine-tune them. One was wrong, but when I sent it the error message, it corrected it and explained the error to me.

It didn't feel like I was relinquishing brain power; in the contrary I learnt things. I could have done that by hand, and I would have learnt far more, but it would have taken months and I don't have months: a bird in the hand is worth two in the bush.

I still think that LLMs are a problem for our societies, but even more so than I thought as it seems to be actually useful in some cases.

I don't like #AI. I think it's problematic in a lot of ways, that I won't repeat here as I believe you heard these (very much true) arguments 100 times.

But #DuckAI helped me quite a lot yesterday, and I don't know how to feel about that. By curiosity, I made it write #elisp code to create new useful commands for #emacs which will help me in my everyday work (for example `C-c m` now creates a PDF using `pdfmom -k` so I don't have to use a terminal at the same time when I use #groff, `C-c t` adds `/|` before some punctuations signs following French typographic rules, …). These functions are very simple, most of you here could have written them by hand in less time than it took me to write the prompts, but I'm no developer, and don't have the time to become one, unfortunately. They work as intended (I can control that as, again, they're simple things), and I more or less understand them, as the #LLM described them. I even asked it questions to understand some parts of the code, and it answered (correctly it seems; I checked and as far as I can know, its answers seem legit), so I was able to modify them by hand to fine-tune them. One was wrong, but when I sent it the error message, it corrected it and explained the error to me.

It didn't feel like I was relinquishing brain power; in the contrary I learnt things. I could have done that by hand, and I would have learnt far more, but it would have taken months and I don't have months: a bird in the hand is worth two in the bush.

I still think that LLMs are a problem for our societies, but even more so than I thought as it seems to be actually useful in some cases.

I don't like #AI. I think it's problematic in a lot of ways, that I won't repeat here as I believe you heard these (very much true) arguments 100 times.

But #DuckAI helped me quite a lot yesterday, and I don't know how to feel about that. By curiosity, I made it write #elisp code to create new useful commands for #emacs which will help me in my everyday work (for example `C-c m` now creates a PDF using `pdfmom -k` so I don't have to use a terminal at the same time when I use #groff, `C-c t` adds `/|` before some punctuations signs following French typographic rules, …). These functions are very simple, most of you here could have written them by hand in less time than it took me to write the prompts, but I'm no developer, and don't have the time to become one, unfortunately. They work as intended (I can control that as, again, they're simple things), and I more or less understand them, as the #LLM described them. I even asked it questions to understand some parts of the code, and it answered (correctly it seems; I checked and as far as I can know, its answers seem legit), so I was able to modify them by hand to fine-tune them. One was wrong, but when I sent it the error message, it corrected it and explained the error to me.

It didn't feel like I was relinquishing brain power; in the contrary I learnt things. I could have done that by hand, and I would have learnt far more, but it would have taken months and I don't have months: a bird in the hand is worth two in the bush.

I still think that LLMs are a problem for our societies, but even more so than I thought as it seems to be actually useful in some cases.

I don't like #AI. I think it's problematic in a lot of ways, that I won't repeat here as I believe you heard these (very much true) arguments 100 times.

But #DuckAI helped me quite a lot yesterday, and I don't know how to feel about that. By curiosity, I made it write #elisp code to create new useful commands for #emacs which will help me in my everyday work (for example `C-c m` now creates a PDF using `pdfmom -k` so I don't have to use a terminal at the same time when I use #groff, `C-c t` adds `/|` before some punctuations signs following French typographic rules, …). These functions are very simple, most of you here could have written them by hand in less time than it took me to write the prompts, but I'm no developer, and don't have the time to become one, unfortunately. They work as intended (I can control that as, again, they're simple things), and I more or less understand them, as the #LLM described them. I even asked it questions to understand some parts of the code, and it answered (correctly it seems; I checked and as far as I can know, its answers seem legit), so I was able to modify them by hand to fine-tune them. One was wrong, but when I sent it the error message, it corrected it and explained the error to me.

It didn't feel like I was relinquishing brain power; in the contrary I learnt things. I could have done that by hand, and I would have learnt far more, but it would have taken months and I don't have months: a bird in the hand is worth two in the bush.

I still think that LLMs are a problem for our societies, but even more so than I thought as it seems to be actually useful in some cases.

@Muemmel

#niri #vim #groff same

Well, a more primitive version of same ;-)

(Also playing with #typst)

@Muemmel

#niri #vim #groff same

Well, a more primitive version of same ;-)

(Also playing with #typst)

@Muemmel

#niri #vim #groff same

Well, a more primitive version of same ;-)

(Also playing with #typst)

@Muemmel

#niri #vim #groff same

Well, a more primitive version of same ;-)

(Also playing with #typst)

On a recent system update, I was alerted to the fact that I had modified a config file(/etc/groff/man.local). Did I want to merge them? Discard them? Fuck if I knew. 😆

.\" man.local - Added 202203 kbowen
.\" Add a searchable string before each section header
.rn SH SH-orig
.de SH
.SH-orig \(sc \\$*

Looking at the diff, I had no recollection of adding these lines. Fortunately for me, my past self was considerate enough to indicate their purpose. Unfortunately for me, my past self failed to credit the source for their inspiration. Bad dog!

I'd really like to read the article where I cribbed this from today.
Better a half-assed comment then no comment at all, I guess. But, still. Do better.

#NoteToSelf #man #manpages #groff #comments

On a recent system update, I was alerted to the fact that I had modified a config file(/etc/groff/man.local). Did I want to merge them? Discard them? Fuck if I knew. 😆

.\" man.local - Added 202203 kbowen
.\" Add a searchable string before each section header
.rn SH SH-orig
.de SH
.SH-orig \(sc \\$*

Looking at the diff, I had no recollection of adding these lines. Fortunately for me, my past self was considerate enough to indicate their purpose. Unfortunately for me, my past self failed to credit the source for their inspiration. Bad dog!

I'd really like to read the article where I cribbed this from today.
Better a half-assed comment then no comment at all, I guess. But, still. Do better.

#NoteToSelf #man #manpages #groff #comments

On a recent system update, I was alerted to the fact that I had modified a config file(/etc/groff/man.local). Did I want to merge them? Discard them? Fuck if I knew. 😆

.\" man.local - Added 202203 kbowen
.\" Add a searchable string before each section header
.rn SH SH-orig
.de SH
.SH-orig \(sc \\$*

Looking at the diff, I had no recollection of adding these lines. Fortunately for me, my past self was considerate enough to indicate their purpose. Unfortunately for me, my past self failed to credit the source for their inspiration. Bad dog!

I'd really like to read the article where I cribbed this from today.
Better a half-assed comment then no comment at all, I guess. But, still. Do better.

#NoteToSelf #man #manpages #groff #comments

On a recent system update, I was alerted to the fact that I had modified a config file(/etc/groff/man.local). Did I want to merge them? Discard them? Fuck if I knew. 😆

.\" man.local - Added 202203 kbowen
.\" Add a searchable string before each section header
.rn SH SH-orig
.de SH
.SH-orig \(sc \\$*

Looking at the diff, I had no recollection of adding these lines. Fortunately for me, my past self was considerate enough to indicate their purpose. Unfortunately for me, my past self failed to credit the source for their inspiration. Bad dog!

I'd really like to read the article where I cribbed this from today.
Better a half-assed comment then no comment at all, I guess. But, still. Do better.

#NoteToSelf #man #manpages #groff #comments

On a recent system update, I was alerted to the fact that I had modified a config file(/etc/groff/man.local). Did I want to merge them? Discard them? Fuck if I knew. 😆

.\" man.local - Added 202203 kbowen
.\" Add a searchable string before each section header
.rn SH SH-orig
.de SH
.SH-orig \(sc \\$*

Looking at the diff, I had no recollection of adding these lines. Fortunately for me, my past self was considerate enough to indicate their purpose. Unfortunately for me, my past self failed to credit the source for their inspiration. Bad dog!

I'd really like to read the article where I cribbed this from today.
Better a half-assed comment then no comment at all, I guess. But, still. Do better.

#NoteToSelf #man #manpages #groff #comments

Where to start with Lauren Groff, author of 'Florida' and 'Brawler'

https://misryoum.com/us/lifestyle/where-to-start-with-lauren-groff-author-of/

On the Shelf If you buy books linked on our site, The Times may earn a commission from Bookshop.org, whose fees support independent bookstores. Across five novels and three story collections, Lauren Groff has merged wide-screen history with intimate...

#Where #start #with #Lauren #Groff #author #Florida #and #Brawler #US_News_Hub #misryoum_com

Textsatz in Groff mit Pdfmom

Zum Textsatz mit Typst wurde hier neulich ein Template vorgestellt. Es gibt unter der gleichen Quelle ebenfalls ein Template für "Groff", insbesondere mit dem Makropaket "mom".

#Textsatz #Groff #Pdfmom #Markdown #Typst #Linux

https://gnulinux.ch/textsatz-in-groff-mit-pdfmom

Textsatz in Groff mit Pdfmom

Zum Textsatz mit Typst wurde hier neulich ein Template vorgestellt. Es gibt unter der gleichen Quelle ebenfalls ein Template für "Groff", insbesondere mit dem Makropaket "mom".

#Textsatz #Groff #Pdfmom #Markdown #Typst #Linux

https://gnulinux.ch/textsatz-in-groff-mit-pdfmom

Textsatz in Groff mit Pdfmom

Zum Textsatz mit Typst wurde hier neulich ein Template vorgestellt. Es gibt unter der gleichen Quelle ebenfalls ein Template für "Groff", insbesondere mit dem Makropaket "mom".

#Textsatz #Groff #Pdfmom #Markdown #Typst #Linux

https://gnulinux.ch/textsatz-in-groff-mit-pdfmom

Textsatz in Groff mit Pdfmom

Zum Textsatz mit Typst wurde hier neulich ein Template vorgestellt. Es gibt unter der gleichen Quelle ebenfalls ein Template für "Groff", insbesondere mit dem Makropaket "mom".

#Textsatz #Groff #Pdfmom #Markdown #Typst #Linux

https://gnulinux.ch/textsatz-in-groff-mit-pdfmom

Textsatz in Groff mit Pdfmom

Zum Textsatz mit Typst wurde hier neulich ein Template vorgestellt. Es gibt unter der gleichen Quelle ebenfalls ein Template für "Groff", insbesondere mit dem Makropaket "mom".

#Textsatz #Groff #Pdfmom #Markdown #Typst #Linux

https://gnulinux.ch/textsatz-in-groff-mit-pdfmom

Jeremy Jordan reemplazará a Jonathan Groff en 'Just in Time' de Broadway #Broadway #Groff #Jeremy #Jonathan #Jordan #reemplazará #Time #ButterWord #Spanish_News Comenta tu opinión 👇
https://butterword.com/jeremy-jordan-reemplazara-a-jonathan-groff-en-just-in-time-de-broadway/?feed_id=66101&_unique_id=69722f13ef305

I can't speak to whether or not #typst is capable of replacing #LaTeX.

That said, it's a pretty neat tool. After poking at the (excellent) documentation and walking through the tutorial, I was able to start building good looking documents without any hand holding.

My use case is "using archaic tools like #groff to avoid fighting with gui/web word processors". If yours is similar, you'll likely enjoy playing with it.

#TechnicalJiggeryPokery
#PlainText

I can't speak to whether or not #typst is capable of replacing #LaTeX.

That said, it's a pretty neat tool. After poking at the (excellent) documentation and walking through the tutorial, I was able to start building good looking documents without any hand holding.

My use case is "using archaic tools like #groff to avoid fighting with gui/web word processors". If yours is similar, you'll likely enjoy playing with it.

#TechnicalJiggeryPokery
#PlainText

I can't speak to whether or not #typst is capable of replacing #LaTeX.

That said, it's a pretty neat tool. After poking at the (excellent) documentation and walking through the tutorial, I was able to start building good looking documents without any hand holding.

My use case is "using archaic tools like #groff to avoid fighting with gui/web word processors". If yours is similar, you'll likely enjoy playing with it.

#TechnicalJiggeryPokery
#PlainText

I can't speak to whether or not #typst is capable of replacing #LaTeX.

That said, it's a pretty neat tool. After poking at the (excellent) documentation and walking through the tutorial, I was able to start building good looking documents without any hand holding.

My use case is "using archaic tools like #groff to avoid fighting with gui/web word processors". If yours is similar, you'll likely enjoy playing with it.

#TechnicalJiggeryPokery
#PlainText

@stafwag

The Hell of it is that grotty actually supports coloured manual pages natively, and has done all along, since the 1990s. Its own manual page is actually in colour.

Debian and others have actually patched hidden flags in to turn grotty's colour and font capabilities off, about a quarter of a century ago, and they're still there.

Simply getting rid of those patched flags makes quite a difference.

https://jdebp.uk/Softwares/nosh/italics-in-manuals.html#Debian

#grotty #groff #man

@stafwag

The Hell of it is that grotty actually supports coloured manual pages natively, and has done all along, since the 1990s. Its own manual page is actually in colour.

Debian and others have actually patched hidden flags in to turn grotty's colour and font capabilities off, about a quarter of a century ago, and they're still there.

Simply getting rid of those patched flags makes quite a difference.

https://jdebp.uk/Softwares/nosh/italics-in-manuals.html#Debian

#grotty #groff #man

@stafwag

The Hell of it is that grotty actually supports coloured manual pages natively, and has done all along, since the 1990s. Its own manual page is actually in colour.

Debian and others have actually patched hidden flags in to turn grotty's colour and font capabilities off, about a quarter of a century ago, and they're still there.

Simply getting rid of those patched flags makes quite a difference.

https://jdebp.uk/Softwares/nosh/italics-in-manuals.html#Debian

#grotty #groff #man

@stafwag

The Hell of it is that grotty actually supports coloured manual pages natively, and has done all along, since the 1990s. Its own manual page is actually in colour.

Debian and others have actually patched hidden flags in to turn grotty's colour and font capabilities off, about a quarter of a century ago, and they're still there.

Simply getting rid of those patched flags makes quite a difference.

https://jdebp.uk/Softwares/nosh/italics-in-manuals.html#Debian

#grotty #groff #man

@stafwag

The Hell of it is that grotty actually supports coloured manual pages natively, and has done all along, since the 1990s. Its own manual page is actually in colour.

Debian and others have actually patched hidden flags in to turn grotty's colour and font capabilities off, about a quarter of a century ago, and they're still there.

Simply getting rid of those patched flags makes quite a difference.

https://jdebp.uk/Softwares/nosh/italics-in-manuals.html#Debian

#grotty #groff #man

I guess I’m doing something of a competition between #Emacs #orgmode export to #LaTeX and lovingly hand-crafted #heirloom #doctools #troff (-me).
I briefly considered an export from #orgmode to #groff (-ms) via #pandoc to see if the two approaches could possibly share anything, but that may be a gulf that is not worth crossing.

One of the macros I had coded up was to present something as a link to its entry in the appendix the first time it appeared on a new page, and ordinary text without link for subsequent mentions on the same page. While I’m sure there is a way to do this in the #TeX universe, I don’t know (yet) if it is considered sufficiently within the #LaTeX mindset to be worth attempting.

Building up from physical to logical to semantic markup feels more natural in #troff. Reaching down from #LaTeX into #TeX to perform computation in your document feels discouraged, doubly so when exporting from #orgmode. It is a wonderful method for planning, organizing, and ultimately creating a beautiful document from a single source file.

Different people want different things out of their typesetting systems. I’m glad to have spent some time in both the #troff and #TeX worlds.

I guess I’m doing something of a competition between #Emacs #orgmode export to #LaTeX and lovingly hand-crafted #heirloom #doctools #troff (-me).
I briefly considered an export from #orgmode to #groff (-ms) via #pandoc to see if the two approaches could possibly share anything, but that may be a gulf that is not worth crossing.

One of the macros I had coded up was to present something as a link to its entry in the appendix the first time it appeared on a new page, and ordinary text without link for subsequent mentions on the same page. While I’m sure there is a way to do this in the #TeX universe, I don’t know (yet) if it is considered sufficiently within the #LaTeX mindset to be worth attempting.

Building up from physical to logical to semantic markup feels more natural in #troff. Reaching down from #LaTeX into #TeX to perform computation in your document feels discouraged, doubly so when exporting from #orgmode. It is a wonderful method for planning, organizing, and ultimately creating a beautiful document from a single source file.

Different people want different things out of their typesetting systems. I’m glad to have spent some time in both the #troff and #TeX worlds.

I guess I’m doing something of a competition between #Emacs #orgmode export to #LaTeX and lovingly hand-crafted #heirloom #doctools #troff (-me).
I briefly considered an export from #orgmode to #groff (-ms) via #pandoc to see if the two approaches could possibly share anything, but that may be a gulf that is not worth crossing.

One of the macros I had coded up was to present something as a link to its entry in the appendix the first time it appeared on a new page, and ordinary text without link for subsequent mentions on the same page. While I’m sure there is a way to do this in the #TeX universe, I don’t know (yet) if it is considered sufficiently within the #LaTeX mindset to be worth attempting.

Building up from physical to logical to semantic markup feels more natural in #troff. Reaching down from #LaTeX into #TeX to perform computation in your document feels discouraged, doubly so when exporting from #orgmode. It is a wonderful method for planning, organizing, and ultimately creating a beautiful document from a single source file.

Different people want different things out of their typesetting systems. I’m glad to have spent some time in both the #troff and #TeX worlds.

I guess I’m doing something of a competition between #Emacs #orgmode export to #LaTeX and lovingly hand-crafted #heirloom #doctools #troff (-me).
I briefly considered an export from #orgmode to #groff (-ms) via #pandoc to see if the two approaches could possibly share anything, but that may be a gulf that is not worth crossing.

One of the macros I had coded up was to present something as a link to its entry in the appendix the first time it appeared on a new page, and ordinary text without link for subsequent mentions on the same page. While I’m sure there is a way to do this in the #TeX universe, I don’t know (yet) if it is considered sufficiently within the #LaTeX mindset to be worth attempting.

Building up from physical to logical to semantic markup feels more natural in #troff. Reaching down from #LaTeX into #TeX to perform computation in your document feels discouraged, doubly so when exporting from #orgmode. It is a wonderful method for planning, organizing, and ultimately creating a beautiful document from a single source file.

Different people want different things out of their typesetting systems. I’m glad to have spent some time in both the #troff and #TeX worlds.

I guess I’m doing something of a competition between #Emacs #orgmode export to #LaTeX and lovingly hand-crafted #heirloom #doctools #troff (-me).
I briefly considered an export from #orgmode to #groff (-ms) via #pandoc to see if the two approaches could possibly share anything, but that may be a gulf that is not worth crossing.

One of the macros I had coded up was to present something as a link to its entry in the appendix the first time it appeared on a new page, and ordinary text without link for subsequent mentions on the same page. While I’m sure there is a way to do this in the #TeX universe, I don’t know (yet) if it is considered sufficiently within the #LaTeX mindset to be worth attempting.

Building up from physical to logical to semantic markup feels more natural in #troff. Reaching down from #LaTeX into #TeX to perform computation in your document feels discouraged, doubly so when exporting from #orgmode. It is a wonderful method for planning, organizing, and ultimately creating a beautiful document from a single source file.

Different people want different things out of their typesetting systems. I’m glad to have spent some time in both the #troff and #TeX worlds.

Don’t get me wrong; I’m reasonably proud of what I have accomplished with #heirloom #doctools (a.k.a. #troff that is not #groff) and I even learned a few neat #makefile tricks along the way. But given how much time I spend with #emacs and #orgmode perhaps I should seriously investigate duplicating or imitating the work in #LaTeX. It did not take as long as I feared it would to get the color and font matters worked out. The #macros look like they will translate easily enough, with some support from #elisp. Links and bookmarks look like they will work themselves out. Pictures could be…interesting.

Don’t get me wrong; I’m reasonably proud of what I have accomplished with #heirloom #doctools (a.k.a. #troff that is not #groff) and I even learned a few neat #makefile tricks along the way. But given how much time I spend with #emacs and #orgmode perhaps I should seriously investigate duplicating or imitating the work in #LaTeX. It did not take as long as I feared it would to get the color and font matters worked out. The #macros look like they will translate easily enough, with some support from #elisp. Links and bookmarks look like they will work themselves out. Pictures could be…interesting.

Don’t get me wrong; I’m reasonably proud of what I have accomplished with #heirloom #doctools (a.k.a. #troff that is not #groff) and I even learned a few neat #makefile tricks along the way. But given how much time I spend with #emacs and #orgmode perhaps I should seriously investigate duplicating or imitating the work in #LaTeX. It did not take as long as I feared it would to get the color and font matters worked out. The #macros look like they will translate easily enough, with some support from #elisp. Links and bookmarks look like they will work themselves out. Pictures could be…interesting.

Don’t get me wrong; I’m reasonably proud of what I have accomplished with #heirloom #doctools (a.k.a. #troff that is not #groff) and I even learned a few neat #makefile tricks along the way. But given how much time I spend with #emacs and #orgmode perhaps I should seriously investigate duplicating or imitating the work in #LaTeX. It did not take as long as I feared it would to get the color and font matters worked out. The #macros look like they will translate easily enough, with some support from #elisp. Links and bookmarks look like they will work themselves out. Pictures could be…interesting.

Am Wochenende doch mal „The Revenant“ geguckt und ordentlich beeindruckt. Direkt danach zufällig quasi das feministische Gegenstück dazu in 2 Tagen durchgelesen und wirklich bewegt.
#Literatur #Groff #Wildnis

Am Wochenende doch mal „The Revenant“ geguckt und ordentlich beeindruckt. Direkt danach zufällig quasi das feministische Gegenstück dazu in 2 Tagen durchgelesen und wirklich bewegt.
#Literatur #Groff #Wildnis

Am Wochenende doch mal „The Revenant“ geguckt und ordentlich beeindruckt. Direkt danach zufällig quasi das feministische Gegenstück dazu in 2 Tagen durchgelesen und wirklich bewegt.
#Literatur #Groff #Wildnis

Am Wochenende doch mal „The Revenant“ geguckt und ordentlich beeindruckt. Direkt danach zufällig quasi das feministische Gegenstück dazu in 2 Tagen durchgelesen und wirklich bewegt.
#Literatur #Groff #Wildnis

Am Wochenende doch mal „The Revenant“ geguckt und ordentlich beeindruckt. Direkt danach zufällig quasi das feministische Gegenstück dazu in 2 Tagen durchgelesen und wirklich bewegt.
#Literatur #Groff #Wildnis

Eine interessante 30minütige Folge Das Wissen vom #SWR über unsere [überwiegend falschen!] Vorstellungen vom #Mittelalter - und deren Korrektur durch moderne Forschung, zu der auch gut das Buch Matrix von Lauren #Groff passt!

[Wenn niemand die Frauennamen hashtaggt, wird man sie auch niemals finden können!]

https://open.spotify.com/episode/4EuNumyDsYrJYvjQPw2LvG?si=d_DasWT1Sd2Ms8wIrw6uRw

Eine interessante 30minütige Folge Das Wissen vom #SWR über unsere [überwiegend falschen!] Vorstellungen vom #Mittelalter - und deren Korrektur durch moderne Forschung, zu der auch gut das Buch Matrix von Lauren #Groff passt!

[Wenn niemand die Frauennamen hashtaggt, wird man sie auch niemals finden können!]

https://open.spotify.com/episode/4EuNumyDsYrJYvjQPw2LvG?si=d_DasWT1Sd2Ms8wIrw6uRw

Eine interessante 30minütige Folge Das Wissen vom #SWR über unsere [überwiegend falschen!] Vorstellungen vom #Mittelalter - und deren Korrektur durch moderne Forschung, zu der auch gut das Buch Matrix von Lauren #Groff passt!

[Wenn niemand die Frauennamen hashtaggt, wird man sie auch niemals finden können!]

https://open.spotify.com/episode/4EuNumyDsYrJYvjQPw2LvG?si=d_DasWT1Sd2Ms8wIrw6uRw

Eine interessante 30minütige Folge Das Wissen vom #SWR über unsere [überwiegend falschen!] Vorstellungen vom #Mittelalter - und deren Korrektur durch moderne Forschung, zu der auch gut das Buch Matrix von Lauren #Groff passt!

[Wenn niemand die Frauennamen hashtaggt, wird man sie auch niemals finden können!]

https://open.spotify.com/episode/4EuNumyDsYrJYvjQPw2LvG?si=d_DasWT1Sd2Ms8wIrw6uRw

Eine interessante 30minütige Folge Das Wissen vom #SWR über unsere [überwiegend falschen!] Vorstellungen vom #Mittelalter - und deren Korrektur durch moderne Forschung, zu der auch gut das Buch Matrix von Lauren #Groff passt!

[Wenn niemand die Frauennamen hashtaggt, wird man sie auch niemals finden können!]

https://open.spotify.com/episode/4EuNumyDsYrJYvjQPw2LvG?si=d_DasWT1Sd2Ms8wIrw6uRw

@pandoc

Actually, this really looks well! I have never been able to manage to write #groff documents, but this looks really well with plain #reStructuredText (or #rst) documents.

@pandoc

Actually, this really looks well! I have never been able to manage to write #groff documents, but this looks really well with plain #reStructuredText (or #rst) documents.

@pandoc

Actually, this really looks well! I have never been able to manage to write #groff documents, but this looks really well with plain #reStructuredText (or #rst) documents.

@pandoc

Actually, this really looks well! I have never been able to manage to write #groff documents, but this looks really well with plain #reStructuredText (or #rst) documents.

(Translations below.)

Textsatzfreunde aufgemerkt: jüngst veröffentlichte ich Version 0.14 des weltweit besten, weil einzigen IDEs für #groff (epischer als LaTeX). Rückmeldung gern gesehen. https://groff.tuxproject.de

(Translations below.)

Textsatzfreunde aufgemerkt: jüngst veröffentlichte ich Version 0.14 des weltweit besten, weil einzigen IDEs für #groff (epischer als LaTeX). Rückmeldung gern gesehen. https://groff.tuxproject.de

(Translations below.)

Textsatzfreunde aufgemerkt: jüngst veröffentlichte ich Version 0.14 des weltweit besten, weil einzigen IDEs für #groff (epischer als LaTeX). Rückmeldung gern gesehen. https://groff.tuxproject.de

(Translations below.)

Textsatzfreunde aufgemerkt: jüngst veröffentlichte ich Version 0.14 des weltweit besten, weil einzigen IDEs für #groff (epischer als LaTeX). Rückmeldung gern gesehen. https://groff.tuxproject.de