On Wednesday, 26 Sep 2018 at 13:11, Kaushal Modi wrote:
> I had been wondering for quite some time (about since 5 months :P) why
> my Org captures have stopped auto-saving.
This has been really annoying me for some time. Thanks for the code you've
posted which I will try out. I use at least 2 i
Hello,
I wanted to replace the cross with a tick (or any arbitrary
symbol) in beamer/latex exports.
I took a look at `org-latex-item' which uses the :checkbox
property to transcode between org and latex/beamer. Looks like I
could change the :checkbox property to enable a custom checkbox,
when i create a new frame,
go to an ancestor of point,
cycle visibility to collapse the entry,
and kill the new frame,
i expect the old frame's point to still be where it was.
instead, it moves to the ancestor of point.
shouldn't point remain inside the invisible region? point can be
different i
Hello,
Is there a way to achieve something like below? See the content in each
nested subtree in the example below.
#+title: Concatenating property values from parent subtrees
* Section
:PROPERTIES
:EXPORT_XYZ: a
:END:
At this point, the value of XYZ property should be "a".
** Sub-section
:PRO
> even when the glyphs have some descent they tend too look more
> naturally (even if imperfectly) aligned at the bottom IMO.
See the attached screenshots for an example of this with an ascent of
90 vs centered.
> Also that suggestion to use org-capture-after-finalize-hook does not
> work.. I am investigating to find the right way.
I got the captures to auto-save with the below work-around:
(with-eval-after-load 'org-capture
(defvar modi/org-capture-base-buffer nil)
(defun modi/org-capture-before-fin
> On Sat, Apr 14, 2018 at 5:43 AM tumashu wrote:
> >
> > Agree this idea, If user want to save-buffer when capture finish, they can
> > add save-buffer to org-capture-after-finalize-hook or just type C-x C-s
Also that suggestion to use org-capture-after-finalize-hook does not
work.. I am invest
On Sat, Apr 14, 2018 at 5:43 AM tumashu wrote:
>
> At 2018-04-14 15:44:00, "Nicolas Goaziou" wrote:
> >Hello,
> >
> >tumashu writes:
> >
> >> I do not know why must save-buffer, may be for information safe :-)
> >
> >If there is no objection, I suggest to simply remove this call to
> >`save-bu
Hi,
Nicolas: I see you point and I should have said baseline not bottom.
Many *inline* formulas are not quite like your examples though and
even when the glyphs have some descent they tend too look more
naturally (even if imperfectly) aligned at the bottom IMO.
Tobias: that's really nice, thanks!
Hello,
> Nicolas Goaziou hat am 26. September 2018 um 12:56
> geschrieben:
>
>
> Hello,
>
> Carlos Pita writes:
> > This was discussed here:
> > https://www.reddit.com/r/emacs/comments/9ggimh/bottom_align_latex_previews_in_org_mode/
> > Here is a screenshot:
> > https://i.redd.it/n83ri6campm
Hello,
stardiviner writes:
> I take a look at the org.el code of functions `org-store-link`,
> `org-insert-link`, they can't inherit the original buffer file name
> `buffer-file-name`.
Why can't they?
> So can't use `org-link-file-path-type 'adaptive` case. But I found
> `org-insert-link` func
Hello,
Carlos Pita writes:
> This was discussed here:
>
> https://www.reddit.com/r/emacs/comments/9ggimh/bottom_align_latex_previews_in_org_mode/
>
> Here is a screenshot:
>
> https://i.redd.it/n83ri6campm11.png
>
> For inline previews centering is clearly suboptimal, after all text in a
> sente
Yes, you are right.
It is my fault.
I am sorry for that.
And thank you for your instruction of minimal config
practice. I should and will follow it.
John Hendy writes:
> On Mon, Sep 24, 2018 at 10:02 PM jiewuza wrote:
>>
>>
>> OMG, it is my fault.
>> I used `C-c C-e l p`
>> My screen is too
Hello,
Kaushal Modi writes:
> I was visiting the Org manual to verify if I got the :only-contents
> parameter of #+include keyword correct, and noticed that that info is
> completely missing from that section in the new org-manual.org.
>
> Reverting back to older texi, it is missing pieces like
14 matches
Mail list logo