> Before I forget, all contributors to GNU ELPA packages have to have
> signed the CA, for any "significant" contribution making up roughly 15
> lines of code or more.  If someone hasn't done so, you can always direct
> them to emacs-devel@gnu.org to request the assignment form.

OK, I'll keep that in mind.

It's definitely not what you'd expect to see in the archive pages. The
end of the message is cut off. I reported a similar issue not long ago,
occuring in the same thread as it happens!

https://lists.sr.ht/~sircmpwn/sr.ht-discuss/%3C87bkvzn17w.fsf%40cosine.blue%3E

Also related: https://todo.sr.ht/~sircmpwn/lists.sr.ht/80

Philip Kaludercic <philipk@posteo.net> writes:

> Also could you apply these changes:
>
> The first and third change are the most important, since ELPA packages
> are officially part of Emacs.
>
> The other ones are just recommendations.

Yep, done. Thanks!

To git.sr.ht:~chambln/aircon-theme.el
   9aea676..4741bd1  master -> master

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.
>
> Have you received any update?

Yes, the copyright assignment was completed yesterday. You can add the

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:

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.

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.

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,

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

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]