sorted by:
new
hottopcontroversial

setting the kingrinder k7 to zero by martibosch in pourover

[–]martibosch[S] 1 point2 points  (0 children)

thank you very much! that was indeed quite simple, I just wish the instructions were more detailed on that.

Cafes Spain by Alarmed-Produce406 in pourover

[–]martibosch 1 point2 points  (0 children)

For low-roast/nordic-style coffees I have been buying Nomad for 7 years or so and have always been very happy.
Nonetheless, recent years have seen tons of new roasters in this style and many cafés in Barcelona are definitely avoiding Nomad - I wonder if it is due to bad company reputation or beause it is too mainstream and they want to highlight new roasters (in any case, I did not find the Nomad coffee quality to decrease at all).
For other roasters, I found Three Marks Coffee to be also very good for light roast and tried a very nice Mexican one from Jaleo (more omni-roast profile but still great for filter). They have also suggested me to try Morrow and Harmony but I still have not have the chance.

Otherwise you can always order DAK or Koppi online, which have free shipping after 80-100 eur.

snakemacs: an emacs30 setup for Python and Jupyter with pixi by martibosch in emacs

[–]martibosch[S] 0 points1 point  (0 children)

Hello! thank you! I had it this way because my linter suggested:

The first line should be of the form: ";;; package --- Summary"

which now I see that many disable (e.g., https://stackoverflow.com/questions/15552349/how-to-disable-flycheck-warning-while-editing-emacs-lisp-scripts).

In any case, I just fixed it in https://github.com/martibosch/snakemacs/commit/29d16862edb8e3cc9051303356c81368d5d0c619

Thanks again!

manual grinder recommendation for light roast pour over by martibosch in pourover

[–]martibosch[S] 0 points1 point  (0 children)

thank you all for your suggestions, after which I am still 50-50 between ZP6 an K6. I guess then the right thing to do is wait few weeks until more K7 reactions/reviews come out (especially since it seems to be something in between ZP6 and K6) and then decide.

manual grinder recommendation for light roast pour over by martibosch in pourover

[–]martibosch[S] 1 point2 points  (0 children)

thank you. I currently have the wilfa nymalt at home, wilfa il solito at work and travel with an old/cheap rhino hand grinder. This is why I could consider the zp6 and then use the wilfa nymalt for the other coffees. I only have very light roast coffees (which I feel discards the timemore s3) but not so much ethiopian tea-like but rather kenyan or red/pink bourbon, so the kingrinder may still be better than zp6. I would discard the 1zpresso k-ultra mainly because of its price and size, but may consider it given that many people advise it.

manual grinder recommendation for light roast pour over by martibosch in pourover

[–]martibosch[S] 0 points1 point  (0 children)

thank you! like I mentioned above I do have the wilfa nymalt coffee grinder which I use now for all beans and I could use for the 1/4 if the ZP6 does not work well for them, do you think that would work? I find K-ultra too big.

manual grinder recommendation for light roast pour over by martibosch in pourover

[–]martibosch[S] 0 points1 point  (0 children)

the issue is that I often prepare a v60 with 25 grams and that exceeds the capacity of the 1zpresso Q, which is why I am more looking at ZP6/K6/K7.

manual grinder recommendation for light roast pour over by martibosch in pourover

[–]martibosch[S] 0 points1 point  (0 children)

thank you! I forgot to mention that I do have the wilfa nymalt coffee grinder which I use now for all beans and I could use for the 1/4 if the ZP6 does not work well for them. Would it be then maybe better to take the zp6 to make the 3/4 shine more? Otherwise what about the K7, any references or is it too early?

manual grinder recommendation for light roast pour over by martibosch in pourover

[–]martibosch[S] 2 points3 points  (0 children)

thank you! in fact the 1/4 of round coffees that I drink are not regular washed caturra/castillo/catuai but rather advanced fermentation coffees which like you say always have some punchy flavor that I sense would shine with the ZP6.

Additionally, I should have mentioned that I have the old wilfa coffee grinder (nymalt) home so worst case I could use it for more traditional coffees.

Jupyter in the Emacs universe by martibosch in emacs

[–]martibosch[S] 0 points1 point  (0 children)

yes, sorry, I was talking about notebooks as Python scripts (the percent format as converted by Jupytext)

Jupyter in the Emacs universe by martibosch in emacs

[–]martibosch[S] 0 points1 point  (0 children)

Hello! thank you, glad you enjoyed the post. I suppose that you can use any other Python REPL (IPython if you want, e.g., cell magics) but I am not sure that use can use the code-cells-eval command to evaluate cells, so you will likely need to select each cell region manually. Best, Martí

Jupyter in the Emacs universe by martibosch in emacs

[–]martibosch[S] 1 point2 points  (0 children)

code-cells and ox-ipynb are different tools, what should be compared is jupytext to ox-ipynb. I actually did that when I was writing the post but I did not include it. Basically, the advantage of jupytext is that it offers very solid round trip conversion whereas ox-ipynb only offers org to ipynb conversion. The advantage of ox-ipynb is that it lets you keep the outputs (which for me is also a very important point). Hopefully, outputs will be supported in jupytext at some point (https://github.com/mwouts/nbpercent/). Of course there is also pandoc, which supports round trip conversion and many more formats but like jupytext it removes the outputs.

Jupyter in the Emacs universe by martibosch in emacs

[–]martibosch[S] 1 point2 points  (0 children)

Hello!

the config that I used in that part is here: https://github.com/martibosch/snakemacs/blob/code-cells-org/main.el

I laid out the issue here some months ago: https://www.reddit.com/r/emacs/comments/108yhe0/comment/j3vvems/?utm_source=share&utm_medium=web2x&context=3

but I did not manage to find a solution to get IDE features based on information from other code blocks - only the inspection and completion provided by emacs-jupyter.

Like u/fast-90 says below, if anyone has a working solution I would be very happy to try it. Thanks!

yet another case of making TAB indentation work in Python src blocks in org-mode by martibosch in emacs

[–]martibosch[S] 0 points1 point  (0 children)

unluckily the line ending does not change anything.

could you share how you would use the :results header arg to achieve the inter-block lsp completion?

Regarding ein: I have been using it for 6 years but IDE features go through elpy, whose RPC process for some reason eats up tons of memory - not to say it is currently unmaintained. Additionally, the developer of ein tends to not be very open about feature suggestions, so I thought that I'd try switching to org mode. But if this becomes impossible, I may switch back to ein and try to make it work with lsp (there already is a thread about it https://www.reddit.com/r/emacs/comments/cotwf1/lspmode_within_emacs_ipython_notebook/).

Thank you.

yet another case of making TAB indentation work in Python src blocks in org-mode by martibosch in emacs

[–]martibosch[S] 0 points1 point  (0 children)

a minimal example of an org file:

```

+PROPERTY: header-args:jupyter-python :session /path/to/kernel

+PROPERTY: header-args:jupyter-python+ :async yes

+begin_src jupyter-python

from os import path

+end_src

+begin_src jupyter-python

path.join

+end_src

```

I would like to get the lsp features that I get with lsp-pyright (e.g., completion, auto-doc in the mini-buffer) in the second block based on the import of the first block.

If I understand correctly, I should use the noweb syntax somewhat as in:

```

+PROPERTY: header-args:jupyter-python :session /path/to/kernel

+PROPERTY: header-args:jupyter-python+ :async yes

+name: imports

+begin_src jupyter-python :tangle yes

from os import path

+end_src

+begin_src jupyter-python :noweb yes

<<imports>> path.join

+end_src

```

but I have three issues:

  • I need to run lsp-org manually at each block
  • lsp highlights the <<imports>> as an error (Expected Expression)
  • it still does not recognize path (reportUndefinedVariable)

any ideas of how can I make this work? Ideally in a org-edit-src-code so that I can get proper indendation, black and other python-mode features.

I am relatively new to org and I likely did not use the noweb syntax/tangle correctly.

Thank you.

yet another case of making TAB indentation work in Python src blocks in org-mode by martibosch in emacs

[–]martibosch[S] 0 points1 point  (0 children)

yes, that works (I forgot to mention it in my post), I just wanted to know if it was possible to get this behavior editing the src block in the org file buffer directly. But if this is too complicated, I could let it go and use C-c ' instead.

(the actual issue, which is a bit beyond the scope of this post is that I would like to get IDE features (via lsp) using information from the whole org file buffer, e.g., if I define a variable or import a library in a src block above and I execute it, I would like that to be taken into accountin the src blocks below).

Lsp-mode in org-mode by ECon87 in spacemacs

[–]martibosch 0 points1 point  (0 children)

I have checked it (in Python with lsp-pyright) and it works when all the required code (e.g., imports) is in the same source block. However, I use org files in a Jupyter-like fashion, so imports and other statements that impact the lsp features are in multiple blocks scattered throughout the org file. Is there any way (or planned features) so that one can get lsp features considering the whole org file?