Jens-Ulrik Petersen skrev:
> Do you want to try adding native compilation your package?
As it turns out, emacs-vm might not be the best package for this
experiment. I could not get VM to work with native compilation.
Instead, I had to turn the native compilation off completely for all
vm*.el files
Jens-Ulrik Petersen skrev:
> Also did you see https://bugs.launchpad.net/vm/+bug/1979048 ?
> It might help you.
Thanks for the pointer.
I haven't looked at that particular report yet. I have tried building
Mark Diekhans' branch "vm-emacs-28" instead of trunk. (Mark is
involved in the bug report I
Hi Göran,
Also did you see https://bugs.launchpad.net/vm/+bug/1979048 ?
It might help you.
On Tue, Aug 9, 2022 at 4:56 PM Göran Uddeborg wrote:
> My package (emacs-vm) was one of the ones that broke with the upgrade
> to Emacs 28 in F36. I'm trying to get it to work again.
>
> One of the issues
On Tue, Aug 9, 2022 at 4:56 PM Göran Uddeborg wrote:
> That brought up a question: what should Emacs add-on packages do when
> it comes to native compilation? Should they build and bundle native
> code? If I understand it correctly, that would mean a new patch build
> of Emacs itself would also r
Hello,
My package (emacs-vm) was one of the ones that broke with the upgrade
to Emacs 28 in F36. I'm trying to get it to work again.
One of the issues is that it shows up a large number of warnings.
After some time I've now understood this is because of the new native
compilation feature. Since m
Uff, that thread has been a … sobering read, on a technical and human level.
Thank you for linking me to it!
Best regards,
Marcus
On 26.07.22 09:58, Peter Oliver wrote:
On Sat, 23 Jul 2022, Marcus Müller wrote:
On 23.07.22 01:37, Peter Oliver wrote:
The emacs developers discourage use of
On Wed, 20 Jul 2022, Dan Čermák wrote:
After the Emacs 28 PR got merged, I went
ahead, built Emacs in Fedora 36 as well and submitted it as an
update
Why, by the way? This isn’t intended to be a veiled criticism, I’m genuinely
interested.
--
Peter Oliver_
On Sat, 23 Jul 2022, Marcus Müller wrote:
On 23.07.22 01:37, Peter Oliver wrote:
The emacs developers discourage use of the GTK-only build on X11. Perhaps
we will want a wrapper to select the most suitable binary.
Oh, I wasn't aware of that, is there somewhere I can read up on that?
See
>From the 28.1 NEWS file: this seems to be a breaking change:
** The WHEN argument of 'make-obsolete' and related functions is mandatory.
> The use of those functions without a WHEN argument was marked obsolete
> back in Emacs 23.1. The affected functions are: 'make-obsolete',
> 'define-obsolete-
Oh, I wasn't aware of that, is there somewhere I can read up on that?
On 23.07.22 01:37, Peter Oliver wrote:
On Mon, 18 Jul 2022, Marcus Müller wrote:
Since the pgtk toolkit supports both X and wayland under the hood, I'd very much
propose that we do not only package an emacs-pgtk binary, but
On Mon, 18 Jul 2022, Marcus Müller wrote:
Since the pgtk toolkit supports both X and wayland under the hood, I'd very
much propose that we do not only package an emacs-pgtk binary, but also, that
it becomes what you get by default (i.e. when you install and run `emacs`).
The emacs developers
On Wed, Jul 20, 2022 at 2:10 PM Dan Čermák
wrote:
> Sorry for breaking your packages Jerry. Maybe we should add some gating
> tests to prevent this kind of breakage in the future. Would you have
> some details what happened?
Bigloo was easy to fix, so no problem there. The pvs-sbcl package
uses
On Fri, 2022-07-22 at 22:50 +0200, Dan Čermák wrote:
> David Malcolm writes:
>
> > On Mon, 2022-07-18 at 13:29 -0400, Ben Cotton wrote:
> > > https://fedoraproject.org/wiki/Changes/Emacs_28
> > >
> > > This document represents a proposed Change. As part of the Changes
> > > process, proposals ar
David Malcolm writes:
> On Mon, 2022-07-18 at 13:29 -0400, Ben Cotton wrote:
>> https://fedoraproject.org/wiki/Changes/Emacs_28
>>
>> This document represents a proposed Change. As part of the Changes
>> process, proposals are publicly announced in order to receive
>> community feedback. This pr
On Mon, 2022-07-18 at 13:29 -0400, Ben Cotton wrote:
> https://fedoraproject.org/wiki/Changes/Emacs_28
>
> This document represents a proposed Change. As part of the Changes
> process, proposals are publicly announced in order to receive
> community feedback. This proposal will only be implemented
On Thu, 21 Jul 2022 at 08:43, Stephen Smoogen wrote:
>
>
> On Wed, 20 Jul 2022 at 16:12, Dan Čermák
> wrote:
>
>> Hi Kevin and all,
>>
>> "Kevin P. Fleming" writes:
>>
>> > On 7/20/22 14:57, Marcus Müller wrote:
>> >> Oh! That comes as a surprise. Let me try a rebuild!
>> >>
>> >> :( I was real
On Wed, 20 Jul 2022 at 16:12, Dan Čermák
wrote:
> Hi Kevin and all,
>
> "Kevin P. Fleming" writes:
>
> > On 7/20/22 14:57, Marcus Müller wrote:
> >> Oh! That comes as a surprise. Let me try a rebuild!
> >>
> >> :( I was really looking forward to emacs-pgtk.
> >>
> > Forgive my relative newbie-ne
On Wed, Jul 20, 2022 at 3:37 PM Kevin P. Fleming wrote:
>
> This week my F36 system got upgraded to Emacs version 28, so it's
> already in F36. How is that possible?
It's possible because we generally rely on packagers to Do The Right
Thing™. There aren't technical restrictions like in some of ou
Hi Kevin and all,
"Kevin P. Fleming" writes:
> On 7/20/22 14:57, Marcus Müller wrote:
>> Oh! That comes as a surprise. Let me try a rebuild!
>>
>> :( I was really looking forward to emacs-pgtk.
>>
> Forgive my relative newbie-ness here, but this proposal is to upgrade
> Emacs to version 28 in F
He Kevin,
oh, true, after all,
dnf info --releasever=36 emacs
agrees with you. Now, I'm kind of confused about the point of the change
proposal?
emacs -nw -q --batch --eval '(message system-configuration-options)' 2>&1 | grep native
compilaion
also tells me that the announced native compilat
On Wed, Jul 20, 2022 at 1:38 PM Kevin P. Fleming wrote:
> Forgive my relative newbie-ness here, but this proposal is to upgrade
> Emacs to version 28 in F37. That seems fine.
>
> This week my F36 system got upgraded to Emacs version 28, so it's
> already in F36. How is that possible?
For even mor
On 7/20/22 14:57, Marcus Müller wrote:
Oh! That comes as a surprise. Let me try a rebuild!
:( I was really looking forward to emacs-pgtk.
Forgive my relative newbie-ness here, but this proposal is to upgrade
Emacs to version 28 in F37. That seems fine.
This week my F36 system got upgraded to
Oh! That comes as a surprise. Let me try a rebuild!
:( I was really looking forward to emacs-pgtk.
Best regards,
Marcus
On 19.07.22 11:53, Jens-Ulrik Petersen wrote:
On Tue, Jul 19, 2022 at 5:14 AM Marcus Müller wrote:
Since the pgtk toolkit supports both X and wayland under the hood, I'
On Tue, Jul 19, 2022 at 5:14 AM Marcus Müller wrote:
> Since the pgtk toolkit supports both X and wayland under the hood, I'd
> very much propose
> that we do not only package an emacs-pgtk binary, but also, that it
> becomes what you get
> by default (i.e. when you install and run `emacs`).
Go
Dear Bhavin,
A big "yay!" for packaging 28.1; I've been running my own emacs.spec modifications to play
around with this, for one reason, and one reason alone:
PGTK support. Without it, emacs is virtually unusable on Wayland on hidpi screens with the
compositors I've used, as xwayland simply
https://fedoraproject.org/wiki/Changes/Emacs_28
This document represents a proposed Change. As part of the Changes
process, proposals are publicly announced in order to receive
community feedback. This proposal will only be implemented if approved
by the Fedora Engineering Steering Committee.
==
26 matches
Mail list logo
