Re: [O] Update for MobileOrg iOS v1.7 released

[Sean Escriva]

On Tue, Jan 31, 2017 at 3:56 AM Alan Schmitt 
wrote:

> On 2017-01-31 03:58, Sean Escriva  writes:
>
> > Hello fellow Org users,
> >
> > After beta testing several builds, the latest updated version of
> > MobileOrg for iOS has finally been released:
> > https://itunes.apple.com/us/app/mobileorg/id634225528?mt=8
> >
> > Functionality is essentially the same as the previous version, just
> > refreshed the various SDKs and updated the Dropbox API due to Dropbox
> > deprecating v1.
> >
> > Please report any bugs to Github:
> https://github.com/MobileOrg/mobileorg/issues
> >
> > Much thanks to Mario Martelli and Boris for their invaluable help
> > getting this release ready.
>
> Thanks a lot for this release. I just gave it a try and it works great.
>
> I have a question about how to choose what to synchronize. Looking at
> the documentation, it seems to be through the index.org file. I tried to
> modify that file but everything is reset at the next org-mobile-push. So
> I tried to set some variables like this:
>
> (setq org-mobile-agendas nil)
> (setq org-mobile-files nil)
>
> and I still have a lot of agendas.
>

This is actually the behavior defined by org-mobile.el in the function
org-mobile-push:
http://orgmode.org/cgit.cgi/org-mode.git/tree/lisp/org-mobile.el#n306
the actual file is created here:
http://orgmode.org/cgit.cgi/org-mode.git/tree/lisp/org-mobile.el#n662

Is it possible to configure org-mobile to have no agenda at all?
>

By default, not that I know of.
Perhaps there's some way to advise org-mobile-create-sumo-agenda to do
something different or essentially nothing, but I generally try to avoid
that.


>
> (My goal is to start adding things one by one as I need them, I have too
> many org files, and too big agendas, to sync them all.)
>

Perhaps you could look at defining a function for org-mobile-pre-push-hook
to empty zero out org-agenda-files, then restore the value in the post-push
hook. I've never tried that though so I don't know how if it would really
work or what side effects there could be.
http://orgmode.org/cgit.cgi/org-mode.git/tree/lisp/org-mobile.el#n202

Sean

[O] dairy-float not working?

[Ken Mankoff]

I have

* Example
SCHEDULED: <%%(diary-float t 0 2)>

Which used to schedule an event on the 2nd sunday of every month. This has 
stopped working a month or two ago. I'm not sure if it is related to recent 
upgrades to Org 9 a few months ago. I'm now using 9.0.4. It works with the 
emacs default 8.2.10. Before I start bisecting a massive init.org file to try 
to find what might have broken this, I wanted to check if "diary-float" is 
working for others.

Thanks,

  -k.

Re: [O] bug org-capture

[Charles Millar]

On 01/31/2017 04:53 PM, Nicolas Goaziou wrote:

Hello,

Charles Millar  writes:


Until yesterday the following capture template worked. A recent fix
may have caused another bug.
snip

Fixed. Thank you.

Regards,


Works fine. thank you.

Charlie Millar

Re: [O] Sync up the org in emacs master to org maint branch?

[Aaron Ecay]

Hi Lars,

2017ko urtarrilak 31an, Lars Ingebrigtsen-ek idatzi zuen:
> 
> John Wiegley  writes:
> 
>> We're moving toward a future where Emacs.git will represent "core
>> Emacs", and only contain what core needs (plus a few historical bits,
>> I'm sure). There should be no argument for keeping a project in core
>> just to gain auxiliary benefits.
> 
> I'm massively unenthusiastic about this future.  Things in ELPA has to
> be backwards-and-forwards compatible with a wide Emacs version range,

This seems like a technical limitation of ELPAʼs current implementation,
rather than a conceptual impossibility.  If ELPA made available (on the
server for downloading, and in the client for installing) old versions
of packages, then users could always be offered the latest compatible
version, but not later incompatible ones.

Developers would have to be a little more diligent about declaring their
packagesʼ dependencies on emacs major versions (or on other packages, if
they depend on parts of core that have migrated to ELPA), but this would
be a small hurdle.

Aaron

PS Speaking of dependency management, Iʼd be more worried that this kind
of approach will accelerate the advent of dependency hell with ELPA
packages...but I think all package repos have to confront that problem
eventually.  So Iʼd file that thought under “inevitable growing pains”
rather than “arguments against”.

-- 
Aaron Ecay

[O] Timezones revisited

[Russell Adams]

I understand that Org's timestamp format does not include timezone
information. Making that change would be an impractical modification.

I'm frequently working with several different timezones and I only
need to store a time stamp converted to my local time.

Does the time stamp input support some form of timezone input? I
checked the manual and tried a few methods and they don't appear
supported.

--
Russell Adamsrlad...@adamsinfoserv.com

PGP Key ID: 0x1160DCB3   http://www.adamsinfoserv.com/

Fingerprint:1723 D8CA 4280 1EC9 557F  66E8 1154 E018 1160 DCB3

Re: [O] footnotes problems in split files on export to latex

[Nicolas Goaziou]

Hello,

Sharon Kimble  writes:

> Also, if I try to insert a footnote inside the parent file it try's to
> renumber the footnotes, which then causes problems with the other child
> files.

I cannot see why it would cause problems with other included files.
Footnote numbers are hermetic across included files. IOW you can
have [fn:1] in the master document and in every included file.

Could you show an ECM?

> The file is only 1.4mbs, but it has does have 23,985 lines and it is
> glacially-slow in navigating the file, and it does take up large
> percentages of CPU usage. Is there any way in which I could somehow make
> emacs change its capabilities to allow files with large number of line
> numbers please?

This is another, unrelated, issue. Please send a profiler report (using
M-x profiler-start ...).

Regards,

-- 
Nicolas Goaziou

Re: [O] Bug: "Tbl -> Calculate -> Which Column?" says "Wrong type argument: commandp, org-table-current-column" [9.0.3 (release_9.0.3-255-g728929 @ /Users/xcy/src/org-mode/lisp/)]

[Nicolas Goaziou]

Hello,

Chunyang Xu  writes:

> In an Org Mode buffer, put point in a table and click
> "Tbl -> Calculate -> Which Column?" in Menu bar, it fails and reports
> the following in the echo area
>
>   Wrong type argument: commandp, org-table-current-column
>
> by looking at the source code of 'org-table-current-column', it is not a
> interactive command. Thus I think it's a bug, although I don't know
> which command it should run.

Fixed. Thank you.

Regards,

-- 
Nicolas Goaziou

Re: [O] org-use-sub-superscripts not used in HTML export

[Nicolas Goaziou]

Hello,

Roland Everaert  writes:

> During HTML export, whatever is the value of org-use-sub-superscripts, the
> undescore in the middle of a word is alway interpreted as subscript.
>
> Example:
>
> _F_irst _L_evel
>
> In this case, if org-use-sub-superscripts has the value {} or nil, I would
> expect to see the first letter of both words to be underlined.  However,
> the rest of each word is displayed as a subscript and the leading _
> character is displayed.
>
> Is this variable for latex only?

Org does not support mid-word emphasis. So you cannot underline a part
of a word with usual emphasis markers.

Also, the variable used to control export of sub/superscripts is
`org-export-with-sub-superscripts'.

Regards,

-- 
Nicolas Goaziou

Re: [O] bug org-capture

[Nicolas Goaziou]

Hello,

Charles Millar  writes:

> Until yesterday the following capture template worked. A recent fix
> may have caused another bug.
>
> (setq org-capture-templates
>
> ;;; tasks todo on a specific date, not appointments
>   (append '(("t" "Todo entries")
> ("ts" "Scheduled" entry
>  (file+headline "/mnt/Data/ActiveFiles/Diary.org" "TODOs")
>  "* TODO %?%^{What do you want to do?} %^g %i\n SCHEDULED:
> %^{enter a timestamp}t\n\t:OTHERINFO:\n\t\t%^{Enter other pertinent
> info} %i\n\t:END:\n\t\tDate Entered %U\n"
>  :empty-lines 1)
>
> ;;; tasks todo date is nice, but not earth shattering
> ("tt" "Target dates" entry
>  (file+headline "/mnt/Data/ActiveFiles/Diary.org" "TODOs")
>  "* TODO %?%^{What do you want to do?} %^g\n %i\
> TARGETDATE: %^{enter a timestamp}t\n\t:OTHERINFO:\n\t\t%^{Enter other
> pertinent info} %i\n\t:END:\n\t\tDate Entered %U\n"
>  :empty-lines 1)
>
> ;;; tasks with definite deadlines
> ("td" "Deadline" entry
>  (file+headline "/mnt/Data/ActiveFiles/Diary.org" "TODOs")
>  "* TODO %?%^{What do you want to do?} %^g\n  %i\
> DEADLINE: %^{enter a timestamp}t\n\t:OTHERINFO:\n\t\t%^{Enter other
> pertinent info} %i\n\t:END:\n\t\tDate Entered %U\n"
>  :empty-lines 1)
>
> ;;; plain vanilla task todo's
> ("tp" "PlainTODO" entry
>  (file+headline "/mnt/Data/ActiveFiles/Diary.org" "TODOs")
>  "* TODO %?%^{What do you want to do?} %i\ %^{enter
> a timestamp}t %^g\n\t:OTHERINFO:\n\t\t%^{Enter other pertinent info}
> %i\n\t:END:\n\t\tDate Entered %U\n"
>  :empty-lines 1))
>
>   org-capture-templates))
>
> I also have a capture for entering my time worked on files
>
> snip
>
> ("s" "timeslip" table-line
>  (file "/mnt/Data/ActiveFiles/timeslips.org")
>   "\| %(org-read-date)\| %^{FileName} %i\| %^{Narrative}
> %i\| %^{Time} %i\| %^{Expense} %i"
>
> snip
>
> Today I called the capture for the TODOs "t", the sub items show up,
> however if I select "s" the capture goes to the timeslip capture.

Fixed. Thank you.

Regards,

-- 
Nicolas Goaziou

[O] Effort esitmates and agenda filtering

[Mikhail Skorzhinskiy]

When I apply some filtering to emacs agenda, total efforts calculation
remain unchanged. As Carsten Dominik said [1], it's due to how filtering
works, and can't be fixed.

Is something have changed since 2009? And if not, is there any new
corner ways or hacks to see total effort caluclation based on filtering?
For example, org-agenda-skip looks pretty good candidate for it.

Tanks!

o Links

[1] https://lists.gnu.org/archive/html/emacs-orgmode/2009-10/msg9.html

--
Skorzhinskiy Mikhail

[O] Bug: Org separates clock out note from the clock line [9.0.4 (9.0.4-elpaplus @ /home/jorge/.emacs.d/elpa/org-plus-contrib-20170124/)]

[Jorge Morais Neto]

Hi.  I have started this instance of GNU Emacs 25.1.91.1 with an empty init
file and then I customized org-log-note-clock-out to t.  Then I created a
new Org buffer with a single level 1 headline, and set property
CLOCK_INTO_DRAWER to nil.  I then clocked in and then out, adding a note.
The note was stored outside any drawer (as requested) and above the clock
line.  Then I clocked in and out again, adding a second note.  The result
was:

  * Teste
:PROPERTIES:
:CLOCK_INTO_DRAWER: nil
:END:
- Teste 2.
- Teste 1.
CLOCK: [2017-01-31 Tue 14:12]--[2017-01-31 Tue 14:13] =>  0:01
CLOCK: [2017-01-31 Tue 14:12]--[2017-01-31 Tue 14:12] =>  0:00

"teste" is Portuguese for "test".

I expected the "Teste 1" line to stay in its place above the corresponding
clock line, like this:

  * Teste
:PROPERTIES:
:CLOCK_INTO_DRAWER: nil
:END:
- Teste 2.
CLOCK: [2017-01-31 Tue 14:12]--[2017-01-31 Tue 14:13] =>  0:01
- Teste 1.
CLOCK: [2017-01-31 Tue 14:12]--[2017-01-31 Tue 14:12] =>  0:00


This bug occurred in my config.  My workaround was to configure Org to add
logs and clock lines into the LOGBOOK drawer.  Then the bug does not
materialize and I get correct result (except that I cannot configure Org the
way I want).

Regards

Emacs  : GNU Emacs 25.1.91.1 (x86_64-unknown-linux-gnu, GTK+ Version 3.18.9)
 of 2016-12-31
Package: Org mode version 9.0.4 (9.0.4-elpaplus @
/home/jorge/.emacs.d/elpa/org-plus-contrib-20170124/)

-- 
• I am Brazilian.  I hope my English is correct and I welcome corrections.
• Please adopt free formats like PDF, ODF, Org, LaTeX, Opus, WebM and 7z.
• Free (as in free speech) software for Android: https://f-droid.org/

Re: [O] How to use .pdf images on Latex export, and .png images on ODT export

[Charles C. Berry]

On Tue, 31 Jan 2017, Giacomo M wrote:


Dear all,

I was wondering what is the best way to include pdf images on latex export 
and png images on odt export (assuming same path, only extension changes). A 
macro like this one:

#+MACRO: figext @@latex:.pdfodt:.png@@
doesn't seem to work.



No, it won't work as Babel runs before the exporter handles the snippets.

Something like this should do.

Run this block or put the code in your init file:

#+BEGIN_SRC emacs-lisp
  (defun org-pdf-if-latex ()
(if (eq (org-bound-and-true-p
org-export-current-backend)
   'latex) "pdf" "png"))
#+END_SRC


This generates pdf for latex and png for all other backends (or no backend 
at all).


#+name: pdf-or-png
#+BEGIN_SRC R :exports both :results graphics :file-ext (org-pdf-if-latex)
plot(rnorm(50))
#+END_SRC

See (info "(org) file-ext")

HTH,

Chuck

Re: [O] Update for MobileOrg iOS v1.7 released

[Guido Van Hoecke]

Hi guys,

On 31 January 2017 at 04:58, Sean Escriva  wrote:

> Hello fellow Org users,
>
> After beta testing several builds, the latest updated version of MobileOrg
> for iOS has finally been released: https://itunes.
> apple.com/us/app/mobileorg/id634225528?mt=8
>

Works like a charm

Thanks for your efforts and dedication!

Guido


>
> Functionality is essentially the same as the previous version, just
> refreshed the various SDKs and updated the Dropbox API due to Dropbox
> deprecating v1.
>
> Please report any bugs to Github: https://github.com/
> MobileOrg/mobileorg/issues
>
> Much thanks to Mario Martelli and Boris for their invaluable help getting
> this release ready.
>
> Sean
>
>

Re: [O] editing orgmode code blocks always indents content..anyway to stop this?

[Nick Dokos]

Xebar Saram  writes:

> On Tue, Jan 31, 2017 at 9:53 AM, Nicolas Goaziou  
> wrote:
>
> org-edit-src-content-indentation
>
> thx Nicolas!
>
> i have this set in my config to '0' see here
>
> #+BEGIN_SRC emacs-lisp  :results none
> ;; don't indent source code
> org-edit-src-content-indentation 0
> ;; don't adapt indentation
> org-adapt-indentation nil
> ;; preserve the indentation inside of source blocks
> org-src-preserve-indentation t
> #+END_SRC
>

I don't understand what you are doing here: this is not lisp code,
unless there is context that you are not telling us about.  How
exactly do you set it to 0 in your config?

Also, have you checked that it is 0 at runtime? C-h v
org-edit-src-content-indentation RET.

-- 
Nick

Re: [O] footnotes problems in split files on export to latex

[Sharon Kimble]

Nicolas Goaziou  writes:

> Hello,
>
> Sharon Kimble  writes:
>
>> I have a very large file that I'm working on into 4 sections and have
>> included the sections like this, in the middle of the main file -
>>
>> #+include: "~/research/drugs/drugs17-a2i.org"
>> #+include: "~/research/drugs/drugs17-k2n.org"
>> #+include: "~/research/drugs/drugs17-o2z.org"
>>
>>
>> And moved the footnotes for each new section over to the
>> relevant #+include: file.
>
> You may have done a mistake during this step. You could use M-x org-lint
> to check each included document separately.
>
> Org is expected to be able to handle included footnotes.
>
Thanks for this Nicolas.

When I do 'org-lint' on "~/research/drugs/drugs17-a2i.org" I get this as a reply

--8<---cut here---start->8---
   535 high  Unknown fuzzy location "What is a bad trip?"
  4101 high  Unknown fuzzy location "Opium"
  4312 high  Unknown fuzzy location "Poppers"
  4312 high  Unknown fuzzy location "Nitrous oxide"
  4358 high  Unknown fuzzy location "Poppers"
--8<---cut here---end--->8---

Which are section headers in different parts of the various files.

Also, if I try to insert a footnote inside the parent file it try's to
renumber the footnotes, which then causes problems with the other child
files. I do have '#+STARTUP: fnadjust' in the preamble of the parent
file. So how can I lock the footnotes to allow me to enter a new
footnote without scrambling the order and sequences of the footnotes in
both parent and child files please?

The file is only 1.4mbs, but it has does have 23,985 lines and it is
glacially-slow in navigating the file, and it does take up large
percentages of CPU usage. Is there any way in which I could somehow make
emacs change its capabilities to allow files with large number of line
numbers please?

Thanks
Sharon.
-- 
A taste of linux = http://www.sharons.org.uk
TGmeds = http://www.tgmeds.org.uk
Debian 8.6, fluxbox 1.3.5-2, emacs 25.1.1.1


signature.asc
Description: PGP signature

Re: [O] Sync up the org in emacs master to org maint branch?

[David Engster]

John Wiegley writes:
>> "DE" == David Engster  writes:
>
> DE> It is a mistake because you are creating more moving targets and bring
> DE> them together very late in the release process. This reduces the amount of
> DE> testing that is done for those packages, so bugs will be noticed later and
> DE> the quality of the relases suffer. It moves even more work into the
> DE> RC-phase, which is already crowded and where people who can fix those bugs
> DE> might not be readily available. It removes those packages from Emacs CI,
> DE> so that breakages due to changes in core are not immediately noticed, and
> DE> often times they have to be fixed not by those who created the breakage,
> DE> but by those who notice them.
>
> These are issues to be fixed in the way ELPA integrates with our development
> process. I recognize today's ELPA may have these drawbacks, but I believe they
> can be fixed.

This really has not much to do with how ELPA works. My points above are
about the underlying concept you are proposing: moving packages out of
Emacs core and hence removing them from current Emacs development, but
still bundling them with the release. It's a have-and-eat-cake concept.

> We're moving toward a future where Emacs.git will represent "core Emacs", and
> only contain what core needs (plus a few historical bits, I'm sure). There
> should be no argument for keeping a project in core just to gain auxiliary
> benefits.

Of the points I raise above, which fall under "just to gain auxiliary
benefits"? I'm honestly confused. I'm specifically talking about the
quality of the Emacs relases.

Also, I currently have no idea how to continue with CEDET, as the future
where development should happen is unclear, and I get the feeling we're
just waisting our time with the ongoing merge.

-David

Re: [O] Sync up the org in emacs master to org maint branch?

[Stefan Monnier]

> It is a mistake because you are creating more moving targets and bring
> them together very late in the release process. This reduces the amount
> of testing that is done for those packages, so bugs will be noticed
> later and the quality of the relases suffer. It moves even more work
> into the RC-phase, which is already crowded and where people who can fix
> those bugs might not be readily available. It removes those packages
> from Emacs CI, so that breakages due to changes in core are not
> immediately noticed, and often times they have to be fixed not by those
> who created the breakage, but by those who notice them.

Indeed, moving something to elpa.git has benefits but also downsides.

Another downside is that ELPA packages need to be compatible with
various Emacs releases, whereas bundled code can happily ignore those
compatibility issues.  Of course, the reverse is true as well: if
CEDET-core is an ELPA package, then CEDET-client packages don't need to
be compatible with older CEDET-core.

I think the most important issue is to avoid duplicating branches.
Moving (parts of) CEDET to elpa.git is/was mostly motivated by the
desire to avoid the difficulties of sync'ing between the Emacs code and
the upstream code, since the elpa.git branch could hopefully evolve
in-sync with the upstream (or could even *be* the uptream), whereas that
was more difficult for the code in emacs.git.

If the CEDET code in emacs.git becomes "the upstream", then moving it to
elpa.git is much less interesting.


Stefan

Re: [O] Sync up the org in emacs master to org maint branch?

[Lars Ingebrigtsen]

David Engster  writes:

>> (Except perhaps CEDET.  There seems to be a lot of merging problems
>> there.)
>
> This is precisely why we're currently moving all development to Emacs
> and abandon the external repo. At least we were planning to...

Oh, great.  One less thing that would be helped by moving to ELPA.  :-)

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no

Re: [O] Sync up the org in emacs master to org maint branch?

[David Engster]

Lars Ingebrigtsen writes:
> The question is: What is the most effective way for Emacs developers to
> spend their time?  I can't really see that anybody has made the case
> that shifting stuff from Emacs core to ELPA will mean less work for...
> well, anybody.
>
> (Except perhaps CEDET.  There seems to be a lot of merging problems
> there.)

This is precisely why we're currently moving all development to Emacs
and abandon the external repo. At least we were planning to...

-David

Re: [O] Sync up the org in emacs master to org maint branch?

[Lars Ingebrigtsen]

John Wiegley  writes:

> So far, all of these arguments against a tighter development integration with
> ELPA have been predicated on the way that ELPA is used today. ELPA is under
> our control; we can adjust our process to suit the needs of Emacs development.

Yes, but external packages lose much of their value if they aren't
developed in a compatible manner.

> LI> Emacs doesn't seem to have a massive surfeit of developers, so I wonder
> LI> where this plan comes from.
>
> It comes from the desire to decouple the development of large, mostly external
> projects, from core Emacs. They don't belong in Emacs.git.

But you're talking about coupling ELPA tighter with core Emacs, too.
"They don't belong" isn't really much of an argument here.

The question is: What is the most effective way for Emacs developers to
spend their time?  I can't really see that anybody has made the case
that shifting stuff from Emacs core to ELPA will mean less work for...
well, anybody.

(Except perhaps CEDET.  There seems to be a lot of merging problems
there.)

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no

[O] Bug: "Tbl -> Calculate -> Which Column?" says "Wrong type argument: commandp, org-table-current-column" [9.0.3 (release_9.0.3-255-g728929 @ /Users/xcy/src/org-mode/lisp/)]

[Chunyang Xu]

In an Org Mode buffer, put point in a table and click
"Tbl -> Calculate -> Which Column?" in Menu bar, it fails and reports
the following in the echo area

  Wrong type argument: commandp, org-table-current-column

by looking at the source code of 'org-table-current-column', it is not a
interactive command. Thus I think it's a bug, although I don't know
which command it should run.

Emacs  : GNU Emacs 25.1.1 (x86_64-apple-darwin16.3.0, Carbon Version 157 AppKit 
1504.76)
 of 2017-01-15
Package: Org mode version 9.0.3 (release_9.0.3-255-g728929 @ 
/Users/xcy/src/org-mode/lisp/)

Re: [O] Sync up the org in emacs master to org maint branch?

[John Wiegley]

> "LI" == Lars Ingebrigtsen  writes:

LI> I'm massively unenthusiastic about this future. Things in ELPA has to be
LI> backwards-and-forwards compatible with a wide Emacs version range, which
LI> makes maintaining things much more work. When you develop things in "Emacs
LI> core", you have one specific target and can make large internal changes
LI> without these considerations.

So far, all of these arguments against a tighter development integration with
ELPA have been predicated on the way that ELPA is used today. ELPA is under
our control; we can adjust our process to suit the needs of Emacs development.

LI> Emacs doesn't seem to have a massive surfeit of developers, so I wonder
LI> where this plan comes from.

It comes from the desire to decouple the development of large, mostly external
projects, from core Emacs. They don't belong in Emacs.git.

-- 
John Wiegley  GPG fingerprint = 4710 CF98 AF9B 327B B80F
http://newartisans.com  60E1 46C4 BD1A 7AC1 4BA2

Re: [O] Sync up the org in emacs master to org maint branch?

[Lars Ingebrigtsen]

John Wiegley  writes:

> We're moving toward a future where Emacs.git will represent "core
> Emacs", and only contain what core needs (plus a few historical bits,
> I'm sure). There should be no argument for keeping a project in core
> just to gain auxiliary benefits.

I'm massively unenthusiastic about this future.  Things in ELPA has to
be backwards-and-forwards compatible with a wide Emacs version range,
which makes maintaining things much more work.  When you develop things
in "Emacs core", you have one specific target and can make large
internal changes without these considerations.

Emacs doesn't seem to have a massive surfeit of developers, so I wonder
where this plan comes from.

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no

[O] org-use-sub-superscripts not used in HTML export

[Roland Everaert]

Hi,

During HTML export, whatever is the value of org-use-sub-superscripts, the
undescore in the middle of a word is alway interpreted as subscript.

Example:

_F_irst _L_evel

In this case, if org-use-sub-superscripts has the value {} or nil, I would
expect to see the first letter of both words to be underlined.  However,
the rest of each word is displayed as a subscript and the leading _
character is displayed.

Is this variable for latex only?

Software Version:
GNU Emacs 25.1.1 (x86_64-unknown-cygwin) of 2016-09-17
Org mode version 9.0.4 (9.0.4-dist @
/cygdrive/c/Users/re/.emacs.d/site-lisp/org-9.0.4/lisp/)


Regards,

Re: [O] Sync up the org in emacs master to org maint branch?

[John Wiegley]

> "DE" == David Engster  writes:

DE> It is a mistake because you are creating more moving targets and bring
DE> them together very late in the release process. This reduces the amount of
DE> testing that is done for those packages, so bugs will be noticed later and
DE> the quality of the relases suffer. It moves even more work into the
DE> RC-phase, which is already crowded and where people who can fix those bugs
DE> might not be readily available. It removes those packages from Emacs CI,
DE> so that breakages due to changes in core are not immediately noticed, and
DE> often times they have to be fixed not by those who created the breakage,
DE> but by those who notice them.

These are issues to be fixed in the way ELPA integrates with our development
process. I recognize today's ELPA may have these drawbacks, but I believe they
can be fixed.

We're moving toward a future where Emacs.git will represent "core Emacs", and
only contain what core needs (plus a few historical bits, I'm sure). There
should be no argument for keeping a project in core just to gain auxiliary
benefits.

-- 
John Wiegley  GPG fingerprint = 4710 CF98 AF9B 327B B80F
http://newartisans.com  60E1 46C4 BD1A 7AC1 4BA2

[O] How to use .pdf images on Latex export, and .png images on ODT export

[Giacomo M]

Dear all,

I was wondering what is the best way to include pdf images on latex 
export and png images on odt export (assuming same path, only extension 
changes). A macro like this one:

#+MACRO: figext @@latex:.pdfodt:.png@@
doesn't seem to work.

Thanks,

Giacomo

[O] bug org-capture

[Charles Millar]

Until yesterday the following capture template worked. A recent fix may 
have caused another bug.


(setq org-capture-templates

;;; tasks todo on a specific date, not appointments
  (append '(("t" "Todo entries")
("ts" "Scheduled" entry
 (file+headline "/mnt/Data/ActiveFiles/Diary.org" "TODOs")
 "* TODO %?%^{What do you want to do?} %^g %i\n SCHEDULED: 
%^{enter a timestamp}t\n\t:OTHERINFO:\n\t\t%^{Enter other pertinent 
info} %i\n\t:END:\n\t\tDate Entered %U\n"

 :empty-lines 1)

;;; tasks todo date is nice, but not earth shattering
("tt" "Target dates" entry
 (file+headline "/mnt/Data/ActiveFiles/Diary.org" "TODOs")
 "* TODO %?%^{What do you want to do?} %^g\n %i\ 
TARGETDATE: %^{enter a timestamp}t\n\t:OTHERINFO:\n\t\t%^{Enter other 
pertinent info} %i\n\t:END:\n\t\tDate Entered %U\n"

 :empty-lines 1)

;;; tasks with definite deadlines
("td" "Deadline" entry
 (file+headline "/mnt/Data/ActiveFiles/Diary.org" "TODOs")
 "* TODO %?%^{What do you want to do?} %^g\n  %i\ DEADLINE: 
%^{enter a timestamp}t\n\t:OTHERINFO:\n\t\t%^{Enter other pertinent 
info} %i\n\t:END:\n\t\tDate Entered %U\n"

 :empty-lines 1)

;;; plain vanilla task todo's
("tp" "PlainTODO" entry
 (file+headline "/mnt/Data/ActiveFiles/Diary.org" "TODOs")
 "* TODO %?%^{What do you want to do?} %i\ %^{enter a 
timestamp}t %^g\n\t:OTHERINFO:\n\t\t%^{Enter other pertinent info} 
%i\n\t:END:\n\t\tDate Entered %U\n"

 :empty-lines 1))

  org-capture-templates))

I also have a capture for entering my time worked on files

snip

("s" "timeslip" table-line
 (file "/mnt/Data/ActiveFiles/timeslips.org")
  "\| %(org-read-date)\| %^{FileName} %i\| %^{Narrative} 
%i\| %^{Time} %i\| %^{Expense} %i"


snip

Today I called the capture for the TODOs "t", the sub items show up, 
however if I select "s" the capture goes to the timeslip capture.


Org mode version 9.0.4 (release_9.0.4-252-g6b30de @ 
/usr/local/share/emacs/site-lisp/org-mode/lisp/)

GNU Emacs 24.4.1 (x86_64-pc-linux-gnu, GTK+ Version 3.14.5) of 
2015-03-07 on trouble, modified by Debian


Charlie Millar

[O] Unable to run ditaa on cygwin emacs

[Roland Everaert]

Hi,

I use Cygwin emacs with Windows UI. I have just installed java 8 (but java
6 is still present for some legacy application) and updated my
.bash_profile with the following:

export JAVA_HOME=/cygdrive/c/tools/java8
export PATH=$PATH:$JAVA_HOME/bin

Org is configured to run ditaa code blocks, but when I evaluate a code
block, I see the following in the *Message* buffer

executing Ditaa code block (TEST)...
java -Dfile.encoding=UTF-8 -jar
/cygdrive/c/Users/re/.emacs.d/site-lisp/org-9.0.4/contrib/scripts/ditaa.jar
/tmp/babel-6316MOI/ditaa-63168iW /cygdrive/c/Users/re/pics/test.png
Error: Unable to access jarfile
/cygdrive/c/Users/re/.emacs.d/site-lisp/org-9.0.4/contrib/scripts/ditaa.jar

Code block evaluation complete.


I am using Org 9.0.4 downloaded today.

The ditaa.jar file has been unblocked in the properties of the file in the
file explorer.

Any idea why I get that error message?

Re: [O] footnotes problems in split files on export to latex

[Nicolas Goaziou]

Hello,

Sharon Kimble  writes:

> I have a very large file that I'm working on into 4 sections and have
> included the sections like this, in the middle of the main file -
>
> #+include: "~/research/drugs/drugs17-a2i.org"
> #+include: "~/research/drugs/drugs17-k2n.org"
> #+include: "~/research/drugs/drugs17-o2z.org"
>
>
> And moved the footnotes for each new section over to the
> relevant #+include: file.

You may have done a mistake during this step. You could use M-x org-lint
to check each included document separately.

Org is expected to be able to handle included footnotes.

Regards,

-- 
Nicolas Goaziou

Re: [O] :results raw for html export problem

[Nicolas Goaziou]

Hello,

Lawrence Bottorff  writes:

> Here's some Lisp in an org file that I export to html
>
> #+begin_src lisp :exports both :results raw

You shouldn't use ":exports both" and ":results raw" together.

With :results raw, Org has no possible way to tell whether the results
of the code block are already inserted in the document or not. Since you
request ":exports both", it always re-generates them upon exporting.

You may want to use ":exports code" and insert results manually in the
buffer.

Regards,

-- 
Nicolas Goaziou

[O] ditaa and plantuml exports source code?

[Andreas Hirczy]

Hi!

Exports from my org files show unwanted source blocks from ditaa in
export. I created a simple example:

###
#+NAME: TEST
#+BEGIN_SRC ditaa :file pics/test.png :exports results
+-+
| cBLU|
| |
|++
||cPNK|
|||
+++
#+END_SRC
###

which translates to ,
including both source and result. The documentation at
 states that
":exports results" is the default for ditaa anyway.

I am rather secure, this worked as intended some time ago; but I get
this behaviour now with at least the following exporters:

 - html
 - latex
 - ODT

I found the same problem with plantuml - see
 for
an example.

Is there anybody who experiences the same behaviuor?

My version of org is
Org mode version 9.0.4 (release_9.0.2-129-g2ac798.dirty @ 
/afs/itp.tugraz.at/user/ahi/.emacs.d/org-mode/lisp/)

Best regards
Andreas
-- 
Andreas Hirczy   https://itp.tugraz.at/~ahi/
Graz University of Technology   phone: +43/316/873-   8190
Institute of Theoretical and Computational Physicsfax: +43/316/873-10 8190
Petersgasse 16, A-8010 Grazmobile: +43/664/859 23 57

[O] footnotes problems in split files on export to latex

[Sharon Kimble]

I have a very large file that I'm working on into 4 sections and have
included the sections like this, in the middle of the main file -

--8<---cut here---start->8---
#+include: "~/research/drugs/drugs17-a2i.org"
#+include: "~/research/drugs/drugs17-k2n.org"
#+include: "~/research/drugs/drugs17-o2z.org"
--8<---cut here---end--->8---

And moved the footnotes for each new section over to the relevant #+include: 
file.

Now when I try to export to latex it replies with this error message -

--8<---cut here---start->8---
(user-error "Definition not found for footnote -4-83") in user-error
--8<---cut here---end--->8---

How can I surmount this problem please?

Thanks
Sharon.
-- 
A taste of linux = http://www.sharons.org.uk
TGmeds = http://www.tgmeds.org.uk
Debian 8.6, fluxbox 1.3.5-2, emacs 25.1.1.1


signature.asc
Description: PGP signature

Re: [O] Update for MobileOrg iOS v1.7 released

[Alan Schmitt]

On 2017-01-31 03:58, Sean Escriva  writes:

> Hello fellow Org users,
>
> After beta testing several builds, the latest updated version of
> MobileOrg for iOS has finally been released:
> https://itunes.apple.com/us/app/mobileorg/id634225528?mt=8 
>
> Functionality is essentially the same as the previous version, just
> refreshed the various SDKs and updated the Dropbox API due to Dropbox
> deprecating v1.
>
> Please report any bugs to Github: 
> https://github.com/MobileOrg/mobileorg/issues 
>
> Much thanks to Mario Martelli and Boris for their invaluable help
> getting this release ready.

Thanks a lot for this release. I just gave it a try and it works great.

I have a question about how to choose what to synchronize. Looking at
the documentation, it seems to be through the index.org file. I tried to
modify that file but everything is reset at the next org-mobile-push. So
I tried to set some variables like this:

(setq org-mobile-agendas nil)
(setq org-mobile-files nil)

and I still have a lot of agendas.

Is it possible to configure org-mobile to have no agenda at all?

(My goal is to start adding things one by one as I need them, I have too
many org files, and too big agendas, to sync them all.)

Thanks,

Alan

-- 
OpenPGP Key ID : 040D0A3B4ED2E5C7
Monthly Athmospheric CO₂, Mauna Loa Obs. 2016-12: 404.48, 2015-12: 401.85


signature.asc
Description: PGP signature

Re: [O] [PATCH] ox-latex.el: Wrap 'minted' src blocks in a 'listing', environment

[Lixin Chin]

Hi,

Thank you, that sounds great. I have not signed the FSF copyright papers.

Regards,
Lixin

On 31/01/2017 04:04 PM, Nicolas Goaziou wrote:

Hello,

Lixin Chin  writes:


Included is a patch to make the 'minted' source code syntax highlighting
package behave the same as the 'listings' source code syntax package
when exporting an org-mode document to LaTeX.

Previously, 'minted' would only get exported to a floating environment
if '#+ATTR_LATEX: :float multicolumn' was provided, whereas the
org-mode documentation implies that it should be floated if any caption
is provided.

Applied. Thank you.

I added TINYCHANGE at the end of the commit message. Please let me know
if you signed FSF papers.


  (memq (plist-get info :latex-listings)
-  '(nil minted)
+  '(nil)

I changed this to

   (null (plist-get info :latex-listings))


Regards,

Re: [O] editing orgmode code blocks always indents content..anyway to stop this?

[Nicolas Goaziou]

Xebar Saram  writes:

> i have this set in my config to '0' see here
>
> #+BEGIN_SRC emacs-lisp  :results none
> ;; don't indent source code
> org-edit-src-content-indentation 0
> ;; don't adapt indentation
> org-adapt-indentation nil
> ;; preserve the indentation inside of source blocks
> org-src-preserve-indentation t
> #+END_SRC
>
> shouldn't that not indent?

It shouldn't. You may want to try with a minimal config, or produce an
ECM. I cannot reproduce your issue.

Regards,

Re: [O] [PATCH] ox-latex.el: Wrap 'minted' src blocks in a 'listing', environment

[Nicolas Goaziou]

Hello,

Lixin Chin  writes:

> Included is a patch to make the 'minted' source code syntax highlighting
> package behave the same as the 'listings' source code syntax package
> when exporting an org-mode document to LaTeX.
>
> Previously, 'minted' would only get exported to a floating environment
> if '#+ATTR_LATEX: :float multicolumn' was provided, whereas the
> org-mode documentation implies that it should be floated if any caption
> is provided.

Applied. Thank you.

I added TINYCHANGE at the end of the commit message. Please let me know
if you signed FSF papers.

>  (memq (plist-get info :latex-listings)
> -  '(nil minted)
> +  '(nil)

I changed this to 

  (null (plist-get info :latex-listings))


Regards,

-- 
Nicolas Goaziou