emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Timothy <tecosaur@gmail.com>
To: Jan Ulrich Hasecke <juh+org-mode@mailbox.org>
Cc: emacs-orgmode@gnu.org
Subject: Re: frustrations
Date: Wed, 01 Dec 2021 20:36:28 +0800	[thread overview]
Message-ID: <87wnkopkk1.fsf@gmail.com> (raw)
In-Reply-To: <Yado1Oq8saqGDPn2@sokrates>

[-- Attachment #1: Type: text/plain, Size: 1747 bytes --]

Hi Jan,

Not that I’m unsympathetic to your issues, however I must say that your email
seems to have little to do with Org, and this *is* the Org mailing list.

Perhaps you would be better served by something like emacs.stackexchange.com.

Jan Ulrich Hasecke <juh+org-mode@mailbox.org> writes:

> Hi all,
>
> after happily using straight for quite a while I am currently frustrated by a
> couple of problems.
>
> In a different thread I asked about exporting citations, which does not
> work for me at all.
>
> Today I discovered that pamparam does not work anymore with an error
> message mentioned here:
> <https://github.com/nobiot/org-transclusion/issues/105>
>
> Even to get to this error, as pamparam didn’t start at all, I had to
> manually fix something in worf.el
> <https://github.com/leotaku/worf/commit/38e901d3888e3a245a5cba14a061bffa1c5fd20b>
>
> If I understand correctly, straight uses the bleeding of packages from
> github. Maybe this is not what I want. Maybe in the past I just was
> lucky not to hit a bug or an incompatible change.
>
> There are some more issues. Startup time of my emacs is more than 30
> seconds even after optimizing something with esup. I have 10.000+ files
> in my org-roam and fear that I hit some limitation either of org-roam or
> my hardware.
>
> How do you configure your emacs using current versions like org 9.5 but
> at the same time avoiding problems with incompatible packages or newly
> introduced bugs?
>
> In a few days I’ll get a new computer and I have serious doubt whether
> to copy my settings.org to the new one, because there are too many
> problems in the last couple of weeks.
>
> Any hints?
> TIA
> juh

All the best,
Timothy

  reply	other threads:[~2021-12-01 12:41 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-01 12:21 frustrations Jan Ulrich Hasecke
2021-12-01 12:36 ` Timothy [this message]
2021-12-01 15:43   ` frustrations Arthur Miller
2021-12-01 12:56 ` frustrations Eric S Fraga
2021-12-01 15:52   ` frustrations Tim Visher
2021-12-01 22:12 ` frustrations Tim Cross
2021-12-03  9:36   ` frustrations juh
2021-12-02  1:41 ` frustrations Ihor Radchenko
2021-12-03 11:51 ` frustrations Dr. Arne Babenhauserheide

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.orgmode.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87wnkopkk1.fsf@gmail.com \
    --to=tecosaur@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=juh+org-mode@mailbox.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).