Hi NoWayman,
> I ran into this with some code I’m writing which checks against
> `lexical-binding’.
> Should the following result in “lexical binding enabled” or
> “lexical binding disabled”?:
Can you think of any examples where this results in different behaviour (without
explicitly checking `le
Hi Ryan,
I’ve just had a glance, but this looks much better to me than what was proposed
earlier 👍. Hopefully we’ll be able to get some feedback on this from others,
and then see it merged 🙂.
All the best,
Timothy
Hi Tim,
Jorge P. de Morais Neto writes:
> I am sorry, my description of the initial condition was incomplete. To
> reproduce the problem, you cannot simply copy the provided text to an
> Org buffer. You should create the clock timestamps with actual clocking
> commands. So please do the follo
Hi Jorge,
> [1. text/x-diff; 0001-doc-org-manual.org-Drawers-Clarify-M-TAB.patch]…
> Then how about the attached patch? Note that I used a black star to
> indicate the position of point—the convention in the Elisp manual.
> Also, I provided a `+#+texinfo: @noindent' directive so the continuation
My thoughts on this would be that if lexical-bindings is
supposed to be
bound to t, it should be done by eval when it gets a non-nil
value for
it's optional argument. If I execute (eval FORM t) in an emacs
lisp
buffer, it looks like lexical-bind is not set either, so I don't
think
it should
No Wayman writes:
> I ran into this with some code I'm writing which checks against
> `lexical-binding'.
> Should the following result in "lexical binding enabled" or
> "lexical binding disabled"?:
>
> #+begin_src emacs-lisp :lexical t
> (message "lexical binding %sabled" (if lexical-binding
Okay, Had some time to put into this. Much happier with this approach as it
doesn't require any file moving and generally leaves src blocks to their
own devices.
The short version is that specifying ":dir 'attach" for a block uses the
directory from (org-attach-dir) as its working directory and any
I ran into this with some code I'm writing which checks against
`lexical-binding'.
Should the following result in "lexical binding enabled" or
"lexical binding disabled"?:
#+begin_src emacs-lisp :lexical t
(message "lexical binding %sabled" (if lexical-binding "en"
"dis"))
#+end_src
Curren
Le 09 Sep 2021, Marco Wahl a écrit :
> My impression is that org-insert-heading-respect-content should be
> called only with point in a subtree.
>
> The fix would be to signal an error when point is not located in a
> subtree.
>
> Does this sound reasonable?
In a way, yes. I guess that the err
Hi!
"Victor A. Stoichita" writes:
> I see the following behavior which seems erroneous to me :
> - When I issue (org-insert-heading-respect-content) in a brand new org
> buffer, with point at point-min I get the error "Beginning of buffer"
> and no heading is inserted.
> - If I write somethi
Just bumping this.
Another question about where to allow cite elements.
On Fri, Aug 20, 2021 at 4:18 PM Bruce D'Arcus wrote:
>
> So this is a tentative request/question; I'm not really sure the best
> approach here.
>
> This is based on discussion with one of the org-roam-bibtex developers
> abo
The current list of styles and variants included in the oc export
processors was a first step, with a goal to provide a solid starting
point, and citations that are more-or-less portable across the
backends.
But that raises an obvious question: what next?
I'd like, for example, to suggest adding
Hi,
I see the following behavior which seems erroneous to me :
- When I issue (org-insert-heading-respect-content) in a brand new org
buffer, with point at point-min I get the error "Beginning of buffer"
and no heading is inserted.
- If I write something on the 1st line, say "test", but no new
Hi,
Syntax available for date/time prompt is very nice.
I would like to be able to use expressions for my timestamps such as -1h
(1 hour ago) or -30m (30 minutes ago) or -1h30m (1 hour and a half ago)
or +1h (in 1 hour)
Cheers,
pinmacs
[1]
https://orgmode.org/manual/The-date_002ftime-prompt
14 matches
Mail list logo
