From Gregory Chamberlain to ~sircmpwn/sr.ht-discuss
Hi, I noticed a potential bug in the archive view of my mailing list. In the third message of the thread (linked below), there is a text/plain attachment in the _middle_ of the message body. https://lists.sr.ht/~chambln/public-inbox/%3C87wnf5bqv5.fsf%40posteo.net%3E#%3C87pmkjyig7.fsf@posteo.net%3E On the archive page for that thread, the presence of an attachment is not represented in any way. What's more, the remainder of the body is cut off so you can't read the entire message. Notice the message is cut off after this line, where the attachment begins: > fill it out and send it to the right address:
From Gregory Chamberlain to ~chambln/public-inbox
Philip Kaludercic <philipk@posteo.net> writes: > Unless you have already signed the FSF copyright assignment, you should > fill it out and send it to the right address: > > Other than that, I can take care of all the remaining stuff. If you > decide against wanting to sign the CA, I can also add the package to > NonGNU ELPA. Thanks, I've now sent the CA. Greg.
From Gregory Chamberlain to ~chambln/public-inbox
Hi Philip, I'd be delighted to see Aircon added to GNU ELPA. How can we do that? (Sorry for the duplicate message, I forgot to CC the list!) Greg.
From Gregory Chamberlain to ~chambln/public-inbox
Alex <bybor@yandex.ru> writes: > I used this plugin https://github.com/dahu/vim-ipa for something, and > it was pretty handy. But it has a dependency on a base library from > the same author, so I wanted to find something lighter than that. But > it was a pretty smooth experience and I really like the > approach. Gonna use it again. > > As for piping input/output, I'm on Windows, which probably complicates > things. If vim-ipa is what you’re comfortable using, that’s great. It looks like it works by converting a selected region of the buffer,
From Gregory Chamberlain to ~chambln/public-inbox
I had been a Vim user for quite some time before trying Emacs, but I avoided evil-mode and the like because I wanted to learn Emacs "the Emacs way." I wanted to give standard Emacs key bindings a fair chance. Modal editing has its advantages but, after the initial learning curve, I’ve come to appreciate the Emacs way. By the way, I had an idea about inputting IPA symbols that could be used with editors like Vim and Kakoune. What if we had a program that reads from standard input and writes to standard output, doing exactly what the ‘ipa’ input method does in Emacs. It may even be possible with a simple sed program. #!/usr/bin/sed -f
From Gregory Chamberlain to ~chambln/public-inbox
Alex <bybor@yandex.ru> writes: > Could you tell how do you input IPA phonetic symbols in your posts? I > used a vim plugin for this some time ago, I wonder if there is > something simpler/better? Thanks for writing in! At the time, I did not have an elegant way to input IPA symbols. I was mostly copy-pasting from Wiktionary, which was cumbersome. Recently I discovered Emacs has an input method for IPA -- several, in fact! I've now posted an article I was working on which goes into more detail on this.[1]
From Gregory Chamberlain to ~chambln/public-inbox
Hi Peter,
> * Implemented in the most-AWK-compatible script.
>
> Tested to work with `mawk` (default on Ubuntu) and `gawk` (GNU Awk
> installed separately)
Works fine for me with gawk and original-awk. However, testing with
mawk 1.3.3 I get the following error:
mawk: line 6: illegal reference to array list_of_words
Any idea why that might be?
[message trimmed]
From Gregory Chamberlain to ~chambln/public-inbox
Peter Marinov <pmar21@sonic.net> writes: > On Wed, May 19, 2021 at 06:11:42PM +0100, Gregory Chamberlain wrote: >> I suppose gmi could test whether lessgmi is available >> >> if command -v lessgmi >/dev/null 2>&1; then ... >> >> but I am concerned about the growing complexity of gmi. With all the >> initial issues ironed out, it’s already become a bit too big for its >> breeches. Bourne shell is not the right language for complex programs. >> But of course anyone is free to fork gmi and take it in whatever >> direction they like. > > I think the fact that it is written in shell script is the killer
From Gregory Chamberlain to ~chambln/public-inbox
Peter Marinov <pmar21@sonic.net> writes: > I was thinking that the main problem that the formatting has to solve > is wrapping of long lines. The coloring is nice but the wrapping is > what makes the navigation of pages pleasant to read. > > Go to this page for example: > gemini://guardian.shit.cx/uk-news/business/2021/may/19/uk-rail-overhaul-privatised-great-british-railways-/index.gmi > > Another good one is with combination of code sections + quote sections > and long lines in all of them: > gemini://drewdevault.com/2021/05/03/awk-is-the-coolest-tool-you-dont-know.gmi > > Try with and without the gawk script
From Gregory Chamberlain to ~chambln/public-inbox
Hi Peter, You should know that, since my last email, I’ve made a number of changes to gmi inspired by your contributions. I’m quite pleased with the results even if the program is some 13 lines longer for it. Gemtext documents are now rendered with syntax colouring using a portable Awk script embedded in gmi itself. It’s enabled by default, but can be disabled by setting the PAGER environment variable. See the Git log for more details about this. As documented in the readme, gmi still lacks rendering of bold and italic text inline. My Awk skills are limited so, if anyone is able to share a patch for this, that would be ace. Until then I will be