Talk @ ILUGC's July 2022 Meetup

2022-07-09 Thread Raghav Gururajan

Hello Guix!

Indian Linux Users Group - Chennai (ILUGC) is a community started in 
90s. They host monthly meetings on second Saturday of every month.


This month, today (July 9th), at 15:00 IST (09:30 UTC); I am giving a 
talk on Guix.


INFO LINK: https://ilugc.in/ilugc-meet-july-2022/

MEETUP LINK: https://meet.jit.si/ILUGCMeet09072022

Feel free to join if you are available. Apologies for the late e-mail, 
as this was planned so recently.


Regards,
Raghav "RG" Gururajan.


OpenPGP_signature
Description: OpenPGP digital signature


Re: emacs-importmagic help python <3 elisp

2022-07-09 Thread Liliana Marie Prikler
Am Samstag, dem 09.07.2022 um 01:50 -0500 schrieb jgart:
>     #:phases
>     #~(modify-phases %standard-phases
>     (add-after 'python:install 'python:wrap
>   (assoc-ref python:%standard-phases 'wrap)
And when exactly do you run python:install?



Re: emacs-importmagic help python <3 elisp

2022-07-09 Thread jgart
On Sat, 09 Jul 2022 10:47:12 +0200 Liliana Marie Prikler 
 wrote:
> Am Samstag, dem 09.07.2022 um 01:50 -0500 schrieb jgart:
> >     #:phases
> >     #~(modify-phases %standard-phases
> >     (add-after 'python:install 'python:wrap
> >   (assoc-ref python:%standard-phases 'wrap)
> And when exactly do you run python:install?

Hi Liliana,

That was a section I copy pasta'ed from Maxim (emacs-jedi). I think I need to 
re-evaluate what I going to do with this package.

Any thoughts?

>From the "Without MELPA" section 
>https://github.com/anachronic/importmagic.el#without-melpa

> Download both importmagic.el and importmagicserver.py. Place them on a 
> load-path of your emacs directory. For instance: ~/.emacs.d/site-lisp

Some open questions I currently have about this package:

1. Will the following warning section cause any errors/bugs in Guix shell 
environments:

https://github.com/anachronic/importmagic.el#warning

2. Do I need to patch this path? 
https://github.com/anachronic/importmagic.el/blob/master/importmagic.el#L106 

all best,

jgart




Re: emacs-importmagic help python <3 elisp

2022-07-09 Thread Liliana Marie Prikler
Am Samstag, dem 09.07.2022 um 11:57 -0500 schrieb jgart:
> On Sat, 09 Jul 2022 10:47:12 +0200 Liliana Marie Prikler
>  wrote:
> > Am Samstag, dem 09.07.2022 um 01:50 -0500 schrieb jgart:
> > >     #:phases
> > >     #~(modify-phases %standard-phases
> > >     (add-after 'python:install 'python:wrap
> > >   (assoc-ref python:%standard-phases 'wrap)
> > And when exactly do you run python:install?
> 
> Hi Liliana,
> 
> That was a section I copy pasta'ed from Maxim (emacs-jedi). I think I
> need to re-evaluate what I going to do with this package.
Note that emacs-jedi has more phases to copy.

> From the "Without MELPA" section
> https://github.com/anachronic/importmagic.el#without-melpa
> 
> > Download both importmagic.el and importmagicserver.py. Place them
> > on a load-path of your emacs directory. For instance:
> > ~/.emacs.d/site-lisp
See above.

> Some open questions I currently have about this package:
> 
> 1. Will the following warning section cause any errors/bugs in Guix
> shell environments:
> 
> https://github.com/anachronic/importmagic.el#warning
No, the expectation is to place it inside a correct shell, containing
(at least) emacs, emacs-importmagic, and all the python packages you
need.

> 2. Do I need to patch this path?
> https://github.com/anachronic/importmagic.el/blob/master/importmagic.el#L106
>  
Maybe?  It should resolve to the same thing, but patching it might make
more sense.

Cheers



Re: Broken lisp-fill-paragraph post Emacs 28 update

2022-07-09 Thread Maxim Cournoyer
Hi,

Ricardo Wurmus  writes:

> Hi Maxim,
>
>> The problem was introduced in commit 9bf367e1848, which aimed to improve
>> the handling of Elisp docstrings.  To revert to the old version (the one
>> that shipped with Emacs 27), you can put this in your .emacs:
>>
>> (require 'lisp-mode)
>> (defun lisp-fill-paragraph (&optional justify)
>>   (interactive "P")
>>   (or (fill-comment-paragraph justify)
>>   (let ((paragraph-start
>>  (concat paragraph-start
>>  "\\|\\s-*\\([(;\"]\\|\\s-:\\|`(\\|#'(\\)"))
>>  (paragraph-separate
>>   (concat paragraph-separate "\\|\\s-*\".*[,\\.]$"))
>> (fill-column (if (and (integerp emacs-lisp-docstring-fill-column)
>>   (derived-mode-p 'emacs-lisp-mode))
>>  emacs-lisp-docstring-fill-column
>>fill-column)))
>>  (fill-paragraph justify))
>>   ;; Never return nil.
>>   t))
>>
>> For more details, you can refer to the (now closed) upstream bug report
>> here [0].
>>
>> [0]  https://issues.guix.gnu.org/56197
>
> Oof, that’s a frustrating discussion.  Interesting how it took just
> *one* comment to dismiss the new bug report with “the votes are in” :-/
>
> Thanks for the procedure definition above.  Do you think we should
> enable this by default in the guix-devel minor mode?

I went ahead and pushed a changed to our .dir-locals.el file that
reverts the behavior of lisp-fill-paragraph to that of Emacs 27 (see
commit c9fb789fe9) Along with an update to our paredit package, it does
the job.  Let me know if something doesn't work as advertised.

Thanks,

Maxim