Dear Time,
> Tim Cross writes:
> Colin Baxter writes:
>> Hello,
>>
>> When publishing, org-mode inserts the following javascript in the
>> xhtml file:
>>
>> #+begin_src js // @license
>>
magnet:?xt=urn:btih:e95b018ef3580986a04669f1b5879592219e2a7a&dn=pub
Fatih Aydin writes:
> Write a code block in an org file and publish it to a html file. You
> will see that only bottom part of the name of the programming language
> is visible when you hover on it because of the css of that block
> (overflow:auto)
> To fix this, a margin-top can be added.
Ah,
Robby Kiggen | Essential IT writes:
> Hi,
>
> in OrgMode 9.5 it seems that the variables during the tangling of sh
> aren't set/initialized.
>
> For example the block below:
> #+begin_src sh :var str="Hello World" :tangle helloworld.sh
> echo $str
> #+end_src
>
> Gets tangled into:
> echo $str
Junwei Wang writes:
> When exporting orgmode file into HTML file, the exporter "mistakely"
> consider "AC:" as some keyword for linking and the string following
> "AC:" would be something link to.
It looks like org-ref is setting up these links for you. Here's the
relevant bit from the configur
> Sent: Sunday, December 13, 2020 at 6:22 AM
> From: "Jean Louis"
> To: daniela-s...@gmx.it
> Cc: 45...@debbugs.gnu.org
> Subject: bug#45212: org-capture user-error: Abort
>
> * daniela-s...@gmx.it [2020-12-12 23:19]:
> > Emacs fires "user-error: Abort" after pressing "q" to abort org-capture.
> Sent: Sunday, December 13, 2020 at 6:19 AM
> From: "Jean Louis"
> To: daniela-s...@gmx.it
> Cc: to...@tuxteam.de, emacs-orgmode@gnu.org, "Ihor Radchenko"
>
> Subject: Re: Emacs inserts hardwired org-agenda-files variable, overwriting
> user options
>
> * daniela-s...@gmx.it [2020-12-12 05
* Ihor Radchenko [2020-12-13 07:35]:
> > What case scenarios would rely
> > on user quitting capture rather than going ahead with an entry?
>
> For example, I have a custom capture function from email. The email is
> removed from inbox upon capture. However, I would not want to proceed
> with rem
* daniela-s...@gmx.it [2020-12-12 23:19]:
> Emacs fires "user-error: Abort" after pressing "q" to abort org-capture.
Those are error messages invented by programmers who never had any
project supervisor who thinks of users.
If user wish to abort it is not an error. Even if it is error, why it
sh
* daniela-s...@gmx.it [2020-12-12 05:41]:
> > And I think it is possible for anybody regardless of programming skill
> > level to make one's own system of management of tasks within less than
> > a week that will get more aligned to personal individualized way of
> > handling tasks, then trying to
> Sent: Sunday, December 13, 2020 at 5:37 AM
> From: "Ihor Radchenko"
> To: daniela-s...@gmx.it
> Cc: 45...@debbugs.gnu.org
> Subject: bug#45212: org-capture user-error: Abort
>
> daniela-s...@gmx.it writes:
>
> > Can't one throw a capture abort signal instead?
>
> Sure, that is possible. Howev
> If you care to share a slightly bigger picture view, particularly about
> the structure of the data you are trying to capture (and/or, your
> workflow) we could likely come up with something that would work much
> better for you than a capture template, at least in this particular
> case.
Most a
daniela-s...@gmx.it writes:
> Can't one throw a capture abort signal instead?
Sure, that is possible. However, consider a possibility that some
external package wants to detect when capture is aborted. If I was
writing such package, I would need to do something like
(condition-case err
(t ))
Johannes Brauer writes:
> Hi!
>
> Trying to export a buffer to html containing
>
> #+TITLE: Titel
> * header
>
> yields the error message:
> apply: Wrong type argument: listp, #("Titel" 0 5 (:parent (#0)))
>
> What can I do?
Thanks for the report and the minimal snippet. I'm not able to trigge
On 2020-12-12 22:49, pie...@caramail.com wrote:
TRS-80 wrote:
Are there any more to these templates you did not show?
Because, (and unless I am missing something) what I see are
essentially
all the same (and quite simple). You would end up with something like
the following in your target fi
Aaron Madlon-Kay writes:
>> + (run-ruby-or-pop-to-buffer
>> + cmd (or session "ruby")
>> + (unless session
>> +(inf-ruby-buffer)))
>
> I have just
> Sent: Sunday, December 13, 2020 at 4:16 AM
> From: "TRS-80"
> To: emacs-orgmode@gnu.org
> Subject: Re: Org Capture Menu cannot be fully viewed
>
> On 2020-12-12 21:08, pie...@caramail.com wrote:
> > Here is one version of a template
> >
> > (setq capture-template-investigation-type '(
> >
> > (
On 2020-12-11 21:35, Jean Louis wrote:
By the way I have completely switched all action management to my
database system with tabulated list mode. No more using Org for action
management, only for document, not even short notes.
It sounds like you have well moved on to another solution by now
On 2020-12-12 21:08, pie...@caramail.com wrote:
Here is one version of a template
(setq capture-template-investigation-type '(
("a" "Historic Background Research Site Evaluation/Testing" entry
(file "~/histr/archaeol.org")
"* Site_Type: %?\n %T\n")
[...]
("u" "Remote Sensing" entry
(f
Thank for the ideas. The 'date' command examples look interesting.
I think R would not be too unwieldy as a hammer here. My use case is a
humble one: just take a several clock times in HH:MM format (utc) and
adjust to another timezone by adding or subtracting the relevant number of
hours. The
I know I can have a headline render to a custom container during export to
html with a property eg HTML_CONTAINER: details
But what If I want an attribute to set the state? Specifically I want the
container to be `` in some situation and just plain
`` in some others.
What are my options?
Thanks
> Sent: Sunday, December 13, 2020 at 3:51 AM
> From: "Ihor Radchenko"
> To: daniela-s...@gmx.it, daniela-s...@gmx.it
> Cc: 45...@debbugs.gnu.org
> Subject: bug#45212: org-capture user-error: Abort
>
> daniela-s...@gmx.it writes:
>
> > Why it is intended? The user wanted to abort and Emacs obey
daniela-s...@gmx.it writes:
> Why it is intended? The user wanted to abort and Emacs obeyed. (q) is an
> option, the user used it,
> and Emacs should not throw an error at the user.
I guess the intention was throwing signal + showing message to user. The
same could certainly be implemented wit
It looks like the two patches are sequential, there should probably be
a rebase into a single patch. I would remove the comment in the second
patch because it is a single command to jump to the default value and
it might change in the future, so no reason to put it in a comment.
One way to communic
Here is one version of a template
(setq capture-template-investigation-type '(
("a" "Historic Background Research Site Evaluation/Testing" entry
(file "~/histr/archaeol.org")
"* Site_Type: %?\n %T\n")
("b" "Systematic Survey Data Recovery/Excavation" entry
(file "~/histr/archaeol.org")
> Sent: Sunday, December 13, 2020 at 2:34 AM
> From: daniela-s...@gmx.it
> To: "Ihor Radchenko"
> Cc: 45...@debbugs.gnu.org
> Subject: bug#45212: org-capture user-error: Abort
>
>
>
> > Sent: Sunday, December 13, 2020 at 2:07 AM
> > From: "Ihor Radchenko"
> > To: daniela-s...@gmx.it, 45...@debbug
> Sent: Sunday, December 13, 2020 at 2:07 AM
> From: "Ihor Radchenko"
> To: daniela-s...@gmx.it, 45...@debbugs.gnu.org
> Subject: bug#45212: org-capture user-error: Abort
>
> daniela-s...@gmx.it writes:
>
> > Emacs fires "user-error: Abort" after pressing "q" to abort org-capture.
>
> This is i
> Sent: Sunday, December 13, 2020 at 1:46 AM
> From: "Tim Cross"
> To: emacs-orgmode@gnu.org
> Subject: Re: Org Capture Menu cannot be fully viewed
>
>
> pie...@caramail.com writes:
>
> > Dear All,
> >
> > When making a relatively long Org Capture Menu for Archaeological Field
> > Management,
> >
Sometimes, we want to nest inline maths expression in \textrm to
handle spaces easily and avoid repetition.
Examples:
1. $A = \{n : \textrm{$n$ odd in $X$}\}$
2. $A = \{n : \textrm{\(n\) odd in \(X\)}\}$
3. \(A = \{n : \textrm{\(n\) odd in \(X\)}\}\)
4. \(A = \{n : \textrm{$n$ odd in $X$}\}\)
ar
On 2020-12-12 15:29, Jussi Norlund wrote:
Hi,
I would like to propose improving the naming of anchor heading links
in primarily HTML and Markdown exports in org-mode.
Here's an example of an implementation of a better naming setup:
http://ivanmalison.github.io/dotfiles/#usemyowndefaultnamingsche
Colin Baxter writes:
> Hello,
>
> When publishing, org-mode inserts the following javascript in the xhtml file:
>
> #+begin_src js
>
> // @license
> magnet:?xt=urn:btih:e95b018ef3580986a04669f1b5879592219e2a7a&dn=public-domain.txt
> Public Domain
>