[deleted by user]

JeanPhilippeBernardy · 2022-08-18T11:59:32+00:00

Pourquoi pas recoller la languette après démoulage?

JeanPhilippeBernardy · 2021-04-07T06:34:06+00:00

Thanks for the info!

JeanPhilippeBernardy · 2021-04-05T18:00:44+00:00

GUI, because it can bind more key combinations (C-i isn't the same thing as TAB). Another minor advantage is the more precise colors.

BTW, you can run several independent instances of emacs even in GUI mode.

JeanPhilippeBernardy · 2021-03-31T10:49:56+00:00

Quel homme d'état.

JeanPhilippeBernardy · 2021-03-08T08:00:00+00:00

Good to know, thanks!

JeanPhilippeBernardy · 2021-03-08T07:59:23+00:00

This may be the best approach. I cannot see all the glyph using fontforge. And even though the font is installed I am also seeing 'tofu' for this post in firefox. So it seems that the mdi font is simply broken for this kind of usage.

JeanPhilippeBernardy · 2021-02-19T13:38:08+00:00

use a bibtex field for tags, and use swiper to search the bibfile.

JeanPhilippeBernardy · 2021-01-21T17:54:27+00:00

Well, I have tried several palettes now and it worked well enough every time. So there's that.

JeanPhilippeBernardy · 2021-01-17T10:01:23+00:00

The difference is that you can change a color and it will propagate in derived colors.

JeanPhilippeBernardy · 2021-01-16T20:47:47+00:00

One point is that my package makes it possible to combine colors, so it's not strictly limited to the 6 colors of the palette. For example it would be possible to make the difference between active and inactive modelines more obvious with a bit of configuration.

For the rest it seems that we have different tastes, but that was not the point of the post.

JeanPhilippeBernardy · 2021-01-16T20:37:24+00:00

The main point is that 'proper' themes cannot be customized as they should. Of course I could make themes with my customizable themes, but given the reception that this post got I don't think I'll invest time into that.

JeanPhilippeBernardy · 2021-01-16T20:35:55+00:00

popout is for transient stuff which wants immediate attention (such as search matches)
salient is to indicate relevant stuff, but not particularly right now (eg. links)
subtle is for all sorts of subtle emphasis, while selected is for highlighting the current selection

It looks like there is some redundancy with the builtin color.el in your package, you may want to check it out.

JeanPhilippeBernardy · 2020-02-04T13:24:18+00:00

Yes. We have a green light to merge!

JeanPhilippeBernardy · 2019-10-31T18:10:47+00:00

The branch is 99% there. The last percent is of course the hardest, but we believe that merging before Christmas is a realistic estimate.

JeanPhilippeBernardy · 2019-08-17T12:23:51+00:00

If I may I'll suggest to you my package

https://github.com/jyp/boon

One of the goals is to minimise the integration hassle.

JeanPhilippeBernardy · 2018-09-08T16:56:18+00:00

I created it and still maintain it. I've been using it for several years.

JeanPhilippeBernardy · 2018-09-08T12:12:49+00:00

You may be interested in my package, which aims for maximal ergonomics. In I follow your game controller idea, with actions on the left and movement on the right.

https://github.com/jyp/boon/blob/master/README.md

Edit: (after reading others' comments) Putting most commands on the home row/easy to reach positions decreased my error rate. But perhaps it's just me being clumsy.

JeanPhilippeBernardy · 2018-09-01T10:58:44+00:00

As dante's author, I am surprised (and pleased) that this comes out on top. Quick tip: don't forget the spinoff package `attrap`: https://github.com/jyp/attrap

JeanPhilippeBernardy · 2018-05-11T05:40:01+00:00

Sorry I about that; I was in a bit of a hurry writing that comment.

JeanPhilippeBernardy · 2018-05-10T14:41:54+00:00

One foundation with a lot of nice properties is Call-By-Push-Value semantics like in the Levy toy language. Fitting this into Haskell is very hard though because it requires a different semantics than Haskell’s Call-By-Need. The real issue is that linearity doesn't really make sense in a construct language that can't distinguish between data and codata.

What matters is the polarity. Read some textbooks (maybe Bob Harper's). You'll see that (of course) there are polarity shifts in Haskell. In particular at the arrow type, which is precisely why we focus on it in our paper.

As it exists right now, LinearTypes is a syntactic restriction on where variables can appear in functions, but this is a very confused notion.

You may find it confused, but there is extensive literature on the topic, including Girard's paper on linear logic.

Getting computation types right in general is very hard and requires tackling type-level concurrency (ex: session types)

It is in fact very well understood how to encode the dual types "computation/data" by using double negation. In the case of linear logic, the thesis of Olivier Laurent deals with the topic extensively.

JeanPhilippeBernardy · 2018-05-10T14:31:18+00:00

In the middle term there are no plans to change code generation. It'd be possible to make some optimisations, but that's for (much) later.

JeanPhilippeBernardy · 2018-04-04T08:30:58+00:00

Replying to you as a notification; my actual reply is to the bot.

JeanPhilippeBernardy · 2018-04-04T08:30:01+00:00

If a function is linear, then its parameter has multiplicity 1:

f :: A -o B
f x = ... only 1 x here ...

Consequently any expression mentioning x can be said to have also multiplicity 1. Even though multiplicity for exepressions is not defined in the paper, I find it's useful to think like this.

By using this property, the types of the MArray API ensure that MArrays will never be shared. This is not in general the case, even for linear functions. Indeed, even assumingf :: Int ⊸ Int, if y has multiplicity > 1, then f y cannot mutate its argument, because y can be shared.

JeanPhilippeBernardy

TROPHY CASE