profile
viewpoint
If you are wondering where the data of this site comes from, please visit https://api.github.com/users/HKey/events. GitMemory does not store any data, but only uses NGINX to cache data for a period of time. The idea behind GitMemory is simply to give users a better reading experience.

HKey/feed-discovery 11

Discover feed url by RSS/Atom autodiscovery.

HKey/dired-atool 9

Pack/unpack files with atool on dired.

HKey/el-init 8

A loader inspired by init-loader

HKey/mozc-temp 7

Use mozc temporarily

HKey/keyset 3

A small library for structuring key bindings.

HKey/caseformat 2

Format based letter case converter

HKey/el-get 2

Manage the external elisp bits and pieces upon which you depend!

HKey/el-init-viewer 2

Record viewer for el-init

HKey/html-fold 1

Provide Emacs the support for hidding and unhidding HTML, XML and SGML elements

push eventmelpa/melpa

Jonas Bernoulli

commit sha b6d136b1033d9afdea965ab07ba7c05e9ecf56e5

Add ol-notmuch recipe

view details

push time in 2 hours

delete branch melpa/melpa

delete branch : ol-notmuch

delete time in 2 hours

create barnchmelpa/melpa

branch : ol-notmuch

created branch time in 2 hours

PR opened melpa/melpa

Add recipe for uci-mode

Brief summary of what the package does

An Emacs major-mode for chess engine interaction. This is a dependency for the more interesting library pygn-mode, to be submitted separately.

Direct link to the package repository

https://github.com/dwcoates/uci-mode

Your association with the package

A contributor, on behalf of @dwcoates .

Relevant communications with the upstream package maintainer

None needed.

Checklist

<!-- Please confirm with x: -->

  • [x] The package is released under a GPL-Compatible Free Software License
  • [x] I've read CONTRIBUTING.org
  • [x] I've used the latest version of package-lint to check for packaging issues, and addressed its feedback
  • [x] My elisp byte-compiles cleanly
  • [x] M-x checkdoc is happy with my docstrings
  • [x] I've built and installed the package using the instructions in CONTRIBUTING.org
  • [ ] I have confirmed some of these without doing them

<!-- After submitting, please fix any problems the CI reports. -->

+3 -0

0 comment

1 changed file

pr created time in 3 hours

PR opened melpa/melpa

add rsync-mode recipe

Brief summary of what the package does

A minor mode to keep repositories in sync using the rsync command line tool.

Direct link to the package repository

https://github.com/r-zip/rsync-mode

Your association with the package

I am the primary author. The only other contributor is ajwhite445. @ajwhite445

Relevant communications with the upstream package maintainer

None needed.

Checklist

<!-- Please confirm with x: -->

  • [x] The package is released under a GPL-Compatible Free Software License
  • [x] I've read CONTRIBUTING.org
  • [x] I've used the latest version of package-lint to check for packaging issues, and addressed its feedback
  • [x] My elisp byte-compiles cleanly
  • [x] M-x checkdoc is happy with my docstrings
  • [x] I've built and installed the package using the instructions in CONTRIBUTING.org
  • [ ] I have confirmed some of these without doing them

<!-- After submitting, please fix any problems the CI reports. -->

+1 -0

0 comment

1 changed file

pr created time in 10 hours

push eventmelpa/melpa

Arif Er

commit sha 45459106a88b5bb8ce5afdef9a7cb95a0fb447bf

Update pippel

view details

push time in 13 hours

PR merged melpa/melpa

Update recipe for pippel

Brief summary of what the package does

A fork of pippel, a package to manage python pip on Emacs.

Direct link to the package repository

https://github.com/arifer612/pippel

Your association with the package

New maintainer of the package.

Relevant communications with the upstream package maintainer

https://github.com/brotzeit/pippel/pull/16#discussion_r653597929

Checklist

<!-- Please confirm with x: -->

  • [x] The package is released under a GPL-Compatible Free Software License
  • [x] I've read CONTRIBUTING.org
  • [x] I've used the latest version of package-lint to check for packaging issues, and addressed its feedback
  • [x] My elisp byte-compiles cleanly
  • [x] M-x checkdoc is happy with my docstrings
  • [x] I've built and installed the package using the instructions in CONTRIBUTING.org
  • [ ] I have confirmed some of these without doing them

<!-- After submitting, please fix any problems the CI reports. -->

+1 -1

0 comment

1 changed file

arifer612

pr closed time in 13 hours

PR opened melpa/melpa

Update recipe for pippel

Brief summary of what the package does

A fork of pippel, a package to manage python pip on Emacs.

Direct link to the package repository

https://github.com/arifer612/pippel

Your association with the package

New maintainer of the package.

Relevant communications with the upstream package maintainer

https://github.com/brotzeit/pippel/pull/16#discussion_r653597929

Checklist

<!-- Please confirm with x: -->

  • [x] The package is released under a GPL-Compatible Free Software License
  • [x] I've read CONTRIBUTING.org
  • [x] I've used the latest version of package-lint to check for packaging issues, and addressed its feedback
  • [x] My elisp byte-compiles cleanly
  • [x] M-x checkdoc is happy with my docstrings
  • [x] I've built and installed the package using the instructions in CONTRIBUTING.org
  • [ ] I have confirmed some of these without doing them

<!-- After submitting, please fix any problems the CI reports. -->

+1 -1

0 comment

1 changed file

pr created time in a day

PR opened melpa/melpa

Add ox-yaow Recipe

Brief summary of what the package does

ox-yaow (yaow=yet another org wiki) is designed to be a lightweight as-is org -> html export option. More detailed information can be found in the README below.

Direct link to the package repository

https://github.com/LaurenceWarne/ox-yaow.el

Your association with the package

Maintainer

Relevant communications with the upstream package maintainer

None Needed

Checklist

<!-- Please confirm with x: -->

  • [x] The package is released under a GPL-Compatible Free Software License
  • [x] I've read CONTRIBUTING.org
  • [x] I've used the latest version of package-lint to check for packaging issues, and addressed its feedback
  • [x] My elisp byte-compiles cleanly
  • [x] M-x checkdoc is happy with my docstrings
  • [x] I've built and installed the package using the instructions in CONTRIBUTING.org
  • [ ] I have confirmed some of these without doing them

<!-- After submitting, please fix any problems the CI reports. -->

+1 -0

0 comment

1 changed file

pr created time in a day

PR closed melpa/melpa

A new recipe for electric-paren

Brief summary of what the package does

electric-paren enables instant execution of complete expressions in interactive Lisp modes, a feature copied from the Symbolics Genera operating system. I.e., when you press the closing ')' in ielm, eshell, interactive-lisp, sly, or slime it executes immediately, without pressing <return>.

Direct link to the package repository

https://github.com/chrchr/electric-paren

Your association with the package

I am the creator

Relevant communications with the upstream package maintainer

Checklist

<!-- Please confirm with x: -->

  • [x ] The package is released under a GPL-Compatible Free Software License
  • [x ] I've read CONTRIBUTING.org
  • [x ] I've used the latest version of package-lint to check for packaging issues, and addressed its feedback
  • [x ] My elisp byte-compiles cleanly
  • [x ] M-x checkdoc is happy with my docstrings
  • [x ] I've built and installed the package using the instructions in CONTRIBUTING.org
  • [ ] I have confirmed some of these without doing them

<!-- After submitting, please fix any problems the CI reports. -->

+1 -0

1 comment

1 changed file

chrchr

pr closed time in 3 days

pull request commentmelpa/melpa

A new recipe for electric-paren

I need to look at this a bit more. I'll resubmit later. Thank you!

chrchr

comment created time in 3 days

PR opened melpa/melpa

Add recipe for project-mode-line-tag

Brief summary of what the package does

Provides a global minor mode to display information about a buffer's project (a "project tag") in its mode line.

A buffer's project tag is derived from either its project.el project's root directory (e.g. bar for /code/foo/bar) or, if present, a dir-local variable named project-mode-line-tag or project-name.

The face applied to the project tag and the format of how to display it in the mode line are fully customizable.

project-mode-line-tag

Direct link to the package repository

https://github.com/fritzgrabo/project-mode-line-tag

Your association with the package

I am the author and the maintainer of this package.

Relevant communications with the upstream package maintainer

None needed

Checklist

  • [x] The package is released under a GPL-Compatible Free Software License
  • [x] I've read CONTRIBUTING.org
  • [x] I've used the latest version of package-lint to check for packaging issues, and addressed its feedback
  • [x] My elisp byte-compiles cleanly, BUT SEE BELOW
  • [x] M-x checkdoc is happy with my docstrings
  • [x] I've built and installed the package using the instructions in CONTRIBUTING.org
  • [ ] I have confirmed some of these without doing them

Compiling under Emacs 28 yields this warning:

In project-mode-line-tag--project-tag:
project-mode-line-tag.el:87:60: Warning: ‘project-roots’ is an obsolete
    function (as of 0.3.0); use ‘project-root’ instead.

Please note that I'm using the obsolete function project-roots (vs. its replacement project-root) on purpose here to maintain support for Emacs versions down to 25.1.

+1 -0

0 comment

1 changed file

pr created time in 3 days

push eventmelpa/melpa

Jonas Bernoulli

commit sha 452c6f2768921d73609bb3dd4c70df538c501f54

Remove archived "ox-slimhtml" package

view details

push time in 3 days

release ghsable/chiropractic-masuda

1.0.0

released time in 4 days

pull request commentmelpa/melpa

Add seriesTracker

Quick drive-by comments here:

MELPA would much rather track your default branch, ie. whatever github shows by default. This prevents an issue where developers change their "git flow" (or similar) workflow later and start working on "master" or "main". So I'd suggest just developing on master.

Re. the autoload, you've defined that exactly right for the behaviour you expected. Note that package-initialize is usually what arranges for the the installed packages' autoloads to be evaluated. If you've installed the correct version of the package you can check its seriestracker-autoloads.el file.

MaximeWack

comment created time in 4 days

pull request commentmelpa/melpa

Add seriesTracker

Hi Chris,

Thanks for the feedback!

I renamed the whole project, functions, and vars to seriestracker, and updated the PR text as well as the links and repo name. master is the stable branch and develop the current default branch so it's best if this recipe points to develop. I have added a commit reflecting this and the name change to this PR.
Tell me if you'd prefer I squash these two commits together.

I fixed all remaining byte-compile and package-lint warnings (except for the one with next-line, as using forward-line introduces undesired behavior while next-line does exactly what is meant to be done by the command, so I'm not sure I should use forward-line despite the warning?)

I followed your advice and used eobp and bobp, thanks!

For the non-standard colon separator I only did as magit does ^. - (and fixed it)

I hope the naming convention is now acceptable (I'm not sure I understood what you referred to by "your new function/variable prefixes don't match" as everything was uniformly prefixed with "st-"?)

Lastly, I'm still having difficulties with… autoloading I think?

With this package installed, upon startup all functions named seriestracker- are available, all seriestracker-- ones are not loaded, but seriestracker is also inexistant before any of the seriestracker- is called.
Per the manual I was expecting the exact opposite by using the ;;;###autoload magic comment before (defun seriestracker) (ie only seriestracker would be visible and calling it would load the rest of the package).
Removing the magic comment doesn't change anything and the seriestracker function refuses to load unless I call one of the other functions, (require 'seriestracker), or :demand the package in use-package.

What would I need to do to obtain the desired behavior? (or at least have the seriestracker function available on startup?) (I hope this is not totally out of the scope of this PR!)

Thank you for your help!

MaximeWack

comment created time in 4 days

pull request commentmelpa/melpa

add Citre

Thanks for reviewing!!

One way to make use of this variable is to add the following somewhere in each of your secondary files...

I tried it and it works. But seems package-lint-main-file is not properly marked as a safe local variable (Emacs asks me to confirm it when opening a file that sets package-lint-main-file). I don't know why as some variables in my citre-basic-tools.el use the same technique and they work well... Anyway, due to this reason, I didn't do this fix. Please let me know if this is OK.

... but maybe you're not seeing this on your end -- so you can consider this an fyi.

I do see it with flycheck, but my test suite doesn't warn me about it (I have byte-compilation-error-on-warn set to t). The test suite is run on CI on major versions of Emacs, so far I haven't see this problem. That's weird...

While I an appreciate the optimality you're after, how much time does this save versus relying on the standard autoload facilities? How much time are you really saving by e.g. deferring (require 'citre-lang-c), which is 200 lines long?

  • About the with-eval-after-load forms:

    For now there's no noticeable difference, but we are preparing that in the future someone may create some heavy language support modules for Citre.

    Also, smartparens does basically the same thing, in smartparens-config.el. I actually learned this from it.

  • About the autoload forms:

    These are necessary. The situation is, for example, when the user calls citre-jump:

    • Since it's marked by ;;;###autoload in citre-basic-tools.el, this file is loaded.
    • The files required by this file is loaded. But citre.el isn't one.
    • citre.el is never loaded.

    This means if a user writes (use-package citre ...) in their config, then the :config block is never executed. Due to this reason, I have to explicitely tell Emacs to load citre.el when using the interactive functions.

What if a user only wants citre-auto-enable-citre-mode when editing specific filetypes?

Then they need to write their own config, as README says:

Or, you can read [citre-config.el](citre-config.el), and write your own config.

But I do want to say the situation you described may not be that common:

  • citre-auto-enable-citre-mode tries to find a tags file for the current file. If none exists, then citre-mode won't be loaded. I think it's safe to assume that if a user creates a tags file for a project, then they want to use Citre in it.

  • I can imagine someone who doesn't want Citre for documentations/markup languages. But this is actually useful. For example, you can jump to the definition of a function mentioned in the doc, and you have auto-completion when you write API documents. I find this very handy.

  • If the user still doesn't want certain tools (e.g. auto-completion) for certain filetypes, we have buffer-local variables citre-enable-xref/capf/imenu-integration that they can customize. For example, they can put a function in find-file-hook that checks the major mode and tweak these variables based on it.

AmaiKinono

comment created time in 5 days

pull request commentmelpa/melpa

Add recipe shellcop

thanks. it's fixed. https://github.com/redguardtoo/shellcop/commit/a5ebf9e3eaf60d35a876c858f63e2c7811ba9a5d

redguardtoo

comment created time in 5 days

pull request commentmelpa/melpa

Add seriesTracker

I'll hop in with a couple answers and some feedback, too.

The package, variable names, and function names should all use the same prefix (in this case your package is still unconventionally named, and your new function/variable prefixes don't match). MELPA doesn't care about the name of the repository, but sometimes it's good if it matches. As for the name itself, arguably st is a little on the short and ambiguous side. It may feel inconvenient, but this is a simple and fair way to prevent namespace collisions across MELPA (and hopefully elsewhere).

Is it okay if I update this PR with a recipe that points to the develop branch so that I don't have to release to master for every update?

If it's helpful for you, I can check your develop branch instead of your default branch while this PR is open. That'll be easier than you changing this PR's recipe file. In general we prefer it if MELPA can index the latest version of your code on the current default branch, and we use MELPA stable (q.v.) if you want to be explicit about tagging release versions.

That said, here's some quick automated feedback on the current develop branch:

byte-compile (using Emacs 27.1):

seriesTracker.el:188:31:Warning: assignment to free variable `series-index'
seriesTracker.el:195:15:Warning: reference to free variable `series-index'
In st--refresh:
seriesTracker.el:327:14:Warning: reference to free variable `st--fold-cycle'
In st-next-line:
seriesTracker.el:440:4:Warning: `next-line' is for interactive use only; use
    `forward-line' instead.
In end of data:
seriesTracker.el:1153:1:Warning: the following functions are not known to be
    defined: acons, first-next-date
  • 651:0: error: st-transient-variable:choice' contains a non-standard separator:', use hyphens instead (see Elisp Coding Conventions). (from package-lint; this one may have been lost in the prefix noise)
  • seriesTracker.el#L608: Could this point/point-max comparison use eobp?
  • seriesTracker.el#L286: Could this point/point-min comparison use bobp?
MaximeWack

comment created time in 5 days

pull request commentmelpa/melpa

add Citre

Thanks for this!

I leave some of the "symbol doesn't start with prefix" errors.

Prefixes look good, but there's a way around this -- see the documentation for package-lint-main-file. One way to make use of this variable is to add the following somewhere in each of your secondary files (just make sure that it isn't inside your ;;; Commentary block):

;; Local variables:
;; package-lint-main-file: "my-main-file.el"
;; end:

Regarding the checklist, I see this only this minor issue on byte-compile (using Emacs 27.1):

citre-peek.el:264:40:Warning: Unknown slot `file'
citre-peek.el:267:45:Warning: Unknown slot `line'

which it seems can be fixed by explicitly requiring xref, but I notice you're deliberately working around that import by using declare-function. I think this isn't a huge issue, but maybe you're not seeing this on your end -- so you can consider this an fyi.

Regarding citre-config.el, this is a fairly unusual interface for a package. I think it would be unfortunate if many packages on MELPA started to be bundled along with lazy load tricks, each implemented in their own idiosyncratic way. While I an appreciate the optimality you're after, how much time does this save versus relying on the standard autoload facilities? How much time are you really saving by e.g. deferring (require 'citre-lang-c), which is 200 lines long? What if a user only wants citre-auto-enable-citre-mode when editing specific filetypes?

AmaiKinono

comment created time in 5 days

push eventmelpa/melpa

Jonas Bernoulli

commit sha cdc15fbd060183e2b06f0c776075beddf7433f39

Update url of dictcc's repository The old url redirects to the new url.

view details

Jonas Bernoulli

commit sha 8ff729d95709a9e0f458e54dbdab4724ca3c09f3

Update url of xresources-theme's repository The old url redirects to the new url.

view details

push time in 5 days

PR opened melpa/melpa

## New recipe for 750words package

Brief summary of what the package does

A library of posting text from Emacs to 750words.com. Also includes an Org exporter for posting text directly from an Org buffer, converting it first to Markdown so that 750words.com renders it correctly.

Direct link to the package repository

https://github.com/zzamboni/750words-client/

Your association with the package

I am the author.

Relevant communications with the upstream package maintainer

None needed.

Checklist

<!-- Please confirm with x: -->

  • [x] The package is released under a GPL-Compatible Free Software License
  • [x] I've read CONTRIBUTING.org
  • [x] I've used the latest version of package-lint to check for packaging issues, and addressed its feedback
  • [x] My elisp byte-compiles cleanly
  • [x] M-x checkdoc is happy with my docstrings
  • [x] I've built and installed the package using the instructions in CONTRIBUTING.org
  • [ ] I have confirmed some of these without doing them

<!-- After submitting, please fix any problems the CI reports. -->

+3 -0

0 comment

1 changed file

pr created time in 5 days

PR opened dimitri/el-get

Fix emms recipe

Without this commit, installation of emms fails with:

make: *** No rule to make target 'autoloads'.  Stop.
+2 -3

0 comment

1 changed file

pr created time in 5 days

release ghsable/chiropractic-masuda

1.0.0

released time in 5 days

push eventdimitri/el-get

Stephan Creutz

commit sha ccca97f2264b64a0474fcc68378ebeb10b72f1e7

Replace cl by cl-lib Since Emacs 27 the package cl is deprecated, the replacement is cl-lib, which is available since Emacs 24.3. This patch replaces cl by cl-lib and drops support for Emacs versions less than 24.3. Dropping older Emacsen is required, because cl-lib is a builtin starting from version 24.3 and doesn't need an extra package from ELPA. Testcases for past issues still contain cl. Most of them seem to be broken and need further investigation. This patch is tested with test/run-ert.sh, which outputs: Ran 10 tests, 10 results as expected, 0 unexpected (2021-01-30 13:24:54+0100, 0.672122 sec) 1 expected failures and manually by daily usage for a month now.

view details

Stephan Creutz

commit sha 7bc810803de735232e69e8326f17dcbc8eefed76

Use cl-mapcan instead of mapcan The function mapcan exists outside cl since Emacs 26.1.

view details

Stephan Creutz

commit sha 5a4fa85f40d77a93cbf102639f3a30c77bc0a2f6

Remove Emacs 23.4 from Github Actions test workflow This change is required, because Emacs 23 doesn't natively provide cl-lib.

view details

Stephan Creutz

commit sha 21a75ba79b4188c32866c4bffe83992722fbaa84

Fix missing requirements

view details

Stephan Creutz

commit sha ac986792c35638bdcfc8b69ecd5a4132d4a82668

Fix position of define-obsolete-variable-alias

view details

Stephan Creutz

commit sha 4d6f30d165cabe20f6e980ec5db1f0b049307f05

Fix lambda invocation for Emacs 28

view details

Stephan Creutz

commit sha ebaa979d2b601a5fefc3a50fc57a662f29784dad

Fix doc string for el-get-verbose Emacs 28 enforces 80 characters per doc string line.

view details

INA Lintaro

commit sha ec135b5353867ce3564a675e99024944b834395d

Merge pull request #2802 from stephan-cr/replace-cl Replace cl by cl-lib

view details

push time in 5 days

PR merged dimitri/el-get

Replace cl by cl-lib

Since Emacs 27 the package cl is deprecated, the replacement is cl-lib, which is available since Emacs 24.3.

This patch replaces cl by cl-lib and drops support for Emacs versions less than 24.3. Dropping older Emacsen is required, because cl-lib is a builtin starting from version 24.3 and doesn't need an extra package from ELPA.

Testcases for past issues (in test/issues) still contain cl. Most of them seem to be broken and need further investigation.

This patch is tested with test/run-ert.sh, which outputs:

Ran 10 tests, 10 results as expected, 0 unexpected (2021-01-30 13:24:54+0100, 0.672122 sec)
1 expected failures

and manually by daily usage for a month now.

This PR addresses issue #2792.

+431 -413

6 comments

28 changed files

stephan-cr

pr closed time in 5 days

PR closed dimitri/el-get

Add Emacs 27.1 to CI

Build el-get for Emacs 27.1 as well.

+1 -0

6 comments

1 changed file

stephan-cr

pr closed time in 5 days

pull request commentdimitri/el-get

Add Emacs 27.1 to CI

Closed, because el-get moved to Github Actions.

stephan-cr

comment created time in 5 days

pull request commentdimitri/el-get

Replace cl by cl-lib

@tarao Fixed all compilation errors. The PR doesn't look nice, because it fixes several unrelated errors, due to unreliable CI. I created a follow-up issue to fix the remaining compilation errors.

stephan-cr

comment created time in 5 days

issue openeddimitri/el-get

Byte compilation should be separately done for each file

$ byte-compile -Werror *.el

... nothing.

$ for i in *.el ; do byte-compile -Werror $i ; done

In toplevel form:
el-get-byte-compile.el:64:9:Error: reference to free variable ‘el-get-byte-compile’

In toplevel form:
el-get-core.el:42:9:Error: reference to free variable ‘el-get-verbose’

In toplevel form:
el-get-dependencies.el:186:1:Error: the function ‘el-get-read-package-with-status’ is not known to be defined.

In toplevel form:
el-get.el:199:28:Error: The compiler ignores ‘autoload’ except at top level.  You should
     probably put the autoload of the macro ‘el-get-bundle’ at top-level.

In toplevel form:
el-get-list-packages.el:452:1:Error: the following functions are not known to be defined: el-get-recipe-filename, el-get-package-type, el-get-package-def, el-get-package-method, el-get-version-to-list, el-get-recipe-pprint, el-get-read-all-recipes

In toplevel form:
el-get-methods.el:46:11:Error: reference to free variable ‘el-get-allow-insecure’

In toplevel form:
el-get-recipes.el:331:1:Error: the function ‘el-get-github-parse-user-and-repo’ is not known to be defined.

In toplevel form:
el-get-status.el:81:21:Error: reference to free variable ‘el-get-status-file’

This issue causes spurious CI failures.

created time in 5 days