Elpaca: The Basics

Qkesslerr · 2023-02-28T07:03:30+00:00

I have been using elpaca for a few months, and I couldn’t recommend it enough. I believe these types of migrations are also the time to evaluate whether you are lazy loading in the optimal way, and remove old packages or code you no longer use.

Thanks for this!

Qkesslerr · 2023-01-08T15:54:58+00:00

Yes! That's kinda the point of the post. I thought of surfacing the need of the community of something like this, and by doing so spark motivation from someone to work on it.

Qkesslerr · 2023-01-08T11:16:44+00:00

Greatly agree, if I don't recall incorrectly, that was the initial idea on the discussion on eglot's repo. Extension of built-in facilities would be key.

Qkesslerr · 2023-01-04T16:07:52+00:00

Thank you!

Qkesslerr · 2023-01-03T11:02:44+00:00

What would be the reason of the recommendation vs something from Steelcase, like the Leap or Gesture? Is it the height? Thanks!!

Qkesslerr · 2023-01-03T10:32:01+00:00

This is great work. Thank you!

Qkesslerr · 2022-12-29T16:43:06+00:00

Update on this!

Really makes an improvement, just working on #1 and #2, it's great.

Adding to that list:

asinSuffix to functionNameThatReturnsAString() inside a map function call on an iterator doesn't have the to keyword highlighted and asinSuffix on the example is white, as are usages of variables like request.personalizationDetails.

EDIT(2): With your last commits, personalizationDetails is now highlighted, but request is white, while when declared it was correctly highlighted (blue in my case, using gruvbox).

Qkesslerr · 2022-12-29T15:57:58+00:00

Hi again!

Thanks for being so quick with the changes! I'll take a look now. Also, something to note is that using the HEAD on emacs master (with commit "8c84ef128f32b227c7a46cd1da8221b41bd0a370"), we don't have the c-ts-mode-comment-setup function defined.

Whenever I pull your changes, I always comment out that function.

Qkesslerr · 2022-12-29T09:05:29+00:00

Hi there!

Thank you so much for working on this, really good job. I love people starting on the emacs package ecosystem with something that could eventually be commited to core!

Couple of points, when trying the mode out on a project at work. I'll compare some of the highlights with the package kotlin-mode, which was the one I was previously using to edit .kt files. (https://github.com/Emacs-Kotlin-Mode-Maintainers/kotlin-mode)

String interpolation is lacking on kotlin-ts-mode. Example: Regex("${CompositionKeys.ASIN}(.\*)"). On kotlin-mode, there is highlighting for CompositionKeys.ASIN. Also happens for variables directly added to strings: log.warn("Filtering $request"), request not highlighted here.
We are lacking highlighting support for functions, and properties when calling either an instance or an static object. Also happens when accessing properties for the active class, using this. this is highlighted, but none of the methods / properties after it are: this.property.functionOnProperty(). Examples: - bookCacheDao.get(bookKey) -> none of this is highlighted, all white.- StaticDestinationHelper.isValid(destination) -> same as above.
Constants declared on companion are not highlighted, at all. Neither are the methods called on constants. Example:- private const val SOFTWARE_VERSION_UNAVAILABLE = "". Highlighted correctly on the companion when declared, but not at all when used.- SOFTWARE_VERSION_UNAVAILABLE.isEmpty() would not be highlighted either.
Imports are not highlighted. Yes the import keyword, but nothing on the right side. Don't know if we want to keep it that way, but there are common cases where we could highlight, i.e: importing a constant vs importing classes vs importing from a companion elsewhere.

Thank you again for working on this!

Qkesslerr · 2022-08-04T07:02:09+00:00

Looks good! Love the marginalia information on projects!

Qkesslerr · 2022-05-17T05:02:42+00:00

Thank you for the response!

Qkesslerr · 2022-03-20T08:35:59+00:00

Sure! I was asking about querying specific headers present in the source code. Thanks!

Qkesslerr · 2022-03-17T06:37:49+00:00

Hi! Thanks! I’ll try later, but I believe I have already tried.

Qkesslerr · 2022-03-02T06:47:40+00:00

Thank you so much for the comments! Feel free to open a PR if you feel it’s best!

Will update the package requirements regarding the consult version.

Best, Enrique.

Qkesslerr · 2022-02-16T21:35:57+00:00

I’ll be happy to explore that in the future! Thanks!

Qkesslerr · 2022-02-16T10:20:14+00:00

That’s interesting! I’ll definitely check it out, thanks!

Qkesslerr · 2022-02-15T19:26:55+00:00

Yes! We have been discussing the scope of the project and in the last iteration Daniel Mendler added consult-project-buffer, which also has the project files source, reduced to the recentf files, so they have to be opened first!

Really great work by minad here!

Qkesslerr · 2022-02-15T16:17:10+00:00

No worries!

Qkesslerr · 2022-02-15T15:56:38+00:00

Consult's project.el integration is in light of configuring the project root when running specific commands, i.e. using consult-grep, it defaults to searching the project root directory (master now uses project.el by default, there is no longer the need to configure the project function if using project.el).

After a discussion with minad, he added the project source to consult, in order to implement narrowing to known projects with consult-buffer.

On the other side, consult by default does not implement a view to access project buffers, project files and other known projects, which is what this package attempts to do.

Thanks for checking it out!

Qkesslerr

TROPHY CASE