Re: [O] clock start time is gone

[Samuel Wales]

On 8/8/17, Nicolas Goaziou  wrote:
> Then I cannot reproduce it. Either from maint or master branch.

i am using vanilla org 9 maint which is recent as of your fixes, emacs
-Q from debian which is 24.4.1, my test case, and this command line:

clocking in produces this bt:

Debugger entered--Lisp error: (wrong-number-of-arguments decode-time 2)
  decode-time(nil t)
  org-clock-get-sum-start()
  #[0 ...
  funcall(#[0 ...
  org-clock-in(nil)
  call-interactively(org-clock-in nil nil)
  command-execute(org-clock-in)

which sounds familiar.  are you using emacs 24?

-- 
The Kafka Pandemic: 

The disease DOES progress. MANY people have died from it. And ANYBODY
can get it at any time.

"You’ve really gotta quit this and get moving, because this is murder
by neglect." ---
.

Re: [O] source block breaks when code looks like heading

[bruce robertson]

I see what you mean now. I haven't tried evaluating the code in the block
yet. I assume it removes the commas automatically.

On Tue, Aug 8, 2017 at 4:03 PM Nicolas Goaziou 
wrote:

> Hello,
>
> bruce robertson  writes:
>
> > How would the source for the math then work?
>
> I'm not sure to understand. Have you tried the suggested solution?
>
> Regards,
>
> --
> Nicolas Goaziou0x80A93738
>

Re: [O] Add-Easy-Template-for-COMMENT-C to org.el

[Grant Rettke]

Hi,

On Mon, Aug 7, 2017 at 4:47 AM, Nicolas Goaziou  wrote:
> Grant Rettke  writes:
>
>> Attached is a patch to an Easy Template binding `C' for `COMMENT'.
> Thank you. Would you mind also adding an entry in ORG-NEWS about it?

Done.

>> The tests had the same 1 failure before and after I made the change
>> "1 unexpected results:
>>FAILED  test-org/refile-get-targets"
>
> FWIW, I do not see the same. Have you set
> `org-refile-target-verify-function' or some other refile-related
> variable that would be different from `org-refile-use-outline-path'?

Yes in my init file I changed a lot of those settings.

Does my init file get used during execution of the tests?


0001-Add-Easy-Template-for-COMMENT-C.patch
Description: Binary data

Re: [O] ox-taskjuggler on MELPA useful despite org-plus-contrib

[Adam Porter]

Tim Cross  writes:

> While there are some minor issues with org-plus-contrib, I find them to
> be minor and mostly due to limitations in package.el (for example,
> dependency on org results in both org-plus-contrib and org packages
> being installed). In fact, I find org-plus-contrib easier to manage than
> just the straight org package as I experience fewer issues arising from
> conflicts with the old 'bundled' version of org in emacs and the package
> version.

I've had the same problem, I have to manually delete the extra org
package now and then.  I wonder if a dummy package would prevent
package.el from reinstalling it...

Re: [O] source block breaks when code looks like heading

[Nicolas Goaziou]

Hello,

bruce robertson  writes:

> How would the source for the math then work?

I'm not sure to understand. Have you tried the suggested solution?

Regards,

-- 
Nicolas Goaziou0x80A93738

[O] [PATCH] Fix two false failures in org's test suite

[Galen Menzel]

Hi all,

A clean clone of org-mode turns up two test failures for me 
(test-org/deadline-close-p and test-org/refile-get-targets), which I 
believe are false failures. The attached (tiny) patch addresses them 
both.


test-org/deadline-close-p fails due to a time zone difference. The test 
assumes that a current time of '(22353 6425 905205 644000) corresponds 
to 2016-06-03 Fri 01:43, but in my timezone it corresponds to 2016-06-02 
Thu 22:43.


test-org/refile-get-targets fails because on macOS /tmp is a symlink to 
/private/tmp, and refile-get-targets resolves symlinks, but the test 
does not.


Best,

GalenFrom 8839e982b2177bd740ef3a88f6a999a30fd62698 Mon Sep 17 00:00:00 2001
From: Galen Menzel 
Date: Tue, 8 Aug 2017 14:31:39 -0700
Subject: [PATCH] test-org.el: Fix two false test failures

* testing/lisp/test-org.el (test-org/deadline-close-p): Fix false
failures due to time-zone differences.
(test-org/refile-get-targets): Fix false failures when test temp-file
path contains a symlink.

TINYCHANGE
---
 testing/lisp/test-org.el | 6 --
 1 file changed, 4 insertions(+), 2 deletions(-)

diff --git a/testing/lisp/test-org.el b/testing/lisp/test-org.el
index 372bf69c3..f2eda045f 100644
--- a/testing/lisp/test-org.el
+++ b/testing/lisp/test-org.el
@@ -375,7 +375,9 @@
   "Test `org-deadline-close-p' specifications."
   ;; Pretend that the current time is 2016-06-03 Fri 01:43
   (cl-letf (((symbol-function 'current-time)
-(lambda () '(22353 6425 905205 644000
+(lambda ()
+  (apply #'encode-time
+ (org-parse-time-string "2016-06-03 Fri 01:43")
 ;; Timestamps are close if they are within `ndays' of lead time.
 (org-test-with-temp-text "* Heading"
   (should (org-deadline-close-p "2016-06-03 Fri" 0))
@@ -5478,7 +5480,7 @@ Paragraph"
   ;; full file name.
   (should
(org-test-with-temp-text-in-file "* H1"
- (let* ((filename (buffer-file-name))
+ (let* ((filename (file-truename (buffer-file-name)))
(org-refile-use-outline-path 'full-file-path)
(org-refile-targets `(((,filename) :level . 1
(member filename (mapcar #'car (org-refile-get-targets))
-- 
2.14.0

Re: [O] ox-taskjuggler on MELPA useful despite org-plus-contrib

[Thomas S. Dye]

Aloha Simon,

Spacemacs has this problem, too.  The solution there is to
byte-recompile org-plus-contrib after an update.

hth,
Tom

Simon Guest writes:

> Hi Nicolas,
>
> My problem with org-plus-contrib exhibited itself when using a .emacs.d
> based on Steve Purcell's, https://github.com/purcell/emacs.d. Specfically,
> when loading ob-R, I got this error:
>
> Invalid function: org-babel-header-args-safe-fn
>
> In response to your email, just now I stripped that config right back to
> basics, and found that my problem went away, and I was able to load ob-R
> after all.  Sorry, I should have done that before.
>
> Having realised that, I think I should report this against Steve Purcell's
> .emacs.d, and leave you guys alone.
>
> Thanks for your help.
>
> cheers,
> Simon
>
> On 8 August 2017 at 19:50, Nicolas Goaziou  wrote:
>
>> Hello,
>>
>> Simon Guest  writes:
>>
>> > Well, almost as soon as I started on that, I see some issues around
>> mixing
>> > old/new org-mode functionality, so this seems like a not-so-good idea
>> after
>> > all.
>> >
>> > In particular, ox-taskjuggler is using the very new org-duration
>> > library.
>>
>> You could use "ox-taskjuggler" from maint.
>>
>> > I'll think of another approach, not using MELPA.
>>
>> I suggest to use GNU ELPA instead.
>>
>> > At least until the underlying problem with org-plus-contrib is
>> > resolved.
>>
>> What exactly is the underlying problem?
>>
>> Regards,
>>
>> --
>> Nicolas Goaziou
>>
>>


--
Thomas S. Dye
http://www.tsdye.com

Re: [O] ox-taskjuggler on MELPA useful despite org-plus-contrib

[Tim Cross]

While there are some minor issues with org-plus-contrib, I find them to
be minor and mostly due to limitations in package.el (for example,
dependency on org results in both org-plus-contrib and org packages
being installed). In fact, I find org-plus-contrib easier to manage than
just the straight org package as I experience fewer issues arising from
conflicts with the old 'bundled' version of org in emacs and the package
version. However, I also use use-package and I don't know to what extent
that impacts my load problems.

I do remember running into a frustrating limitation with org-taskjuggler
when I was using it a couple of years ago - cannot remember the specific
issue now, but do remember I would have to edit the exported taskjuggler
file after every export to adjust some parameters (it might have been
related to default project period, not sure).

Tim



Adam Porter writes:

> Nicolas Goaziou  writes:
>
>>> At least until the underlying problem with org-plus-contrib is
>>> resolved.
>>
>> What exactly is the underlying problem?
>
> FWIW I have been using org-plus-contrib for a while now, and I haven't
> had any problems with my customizations.


--
Tim Cross

Re: [O] ox-taskjuggler on MELPA useful despite org-plus-contrib

[Simon Guest]

Hi Nicolas,

My problem with org-plus-contrib exhibited itself when using a .emacs.d
based on Steve Purcell's, https://github.com/purcell/emacs.d. Specfically,
when loading ob-R, I got this error:

Invalid function: org-babel-header-args-safe-fn

In response to your email, just now I stripped that config right back to
basics, and found that my problem went away, and I was able to load ob-R
after all.  Sorry, I should have done that before.

Having realised that, I think I should report this against Steve Purcell's
.emacs.d, and leave you guys alone.

Thanks for your help.

cheers,
Simon

On 8 August 2017 at 19:50, Nicolas Goaziou  wrote:

> Hello,
>
> Simon Guest  writes:
>
> > Well, almost as soon as I started on that, I see some issues around
> mixing
> > old/new org-mode functionality, so this seems like a not-so-good idea
> after
> > all.
> >
> > In particular, ox-taskjuggler is using the very new org-duration
> > library.
>
> You could use "ox-taskjuggler" from maint.
>
> > I'll think of another approach, not using MELPA.
>
> I suggest to use GNU ELPA instead.
>
> > At least until the underlying problem with org-plus-contrib is
> > resolved.
>
> What exactly is the underlying problem?
>
> Regards,
>
> --
> Nicolas Goaziou
>
>

[O] how do you get an OPTIONS value during export?

[John Kitchin]

Hi,

In my ipynb exporter, I generate md strings for cells using something like

(org-export-string-as
s
'md t '(:with-toc nil :with-tags nil))

This works unless there is a broken link:

https://github.com/jkitchin/ox-ipynb/issues/2#issuecomment-321061051

I figured out I can make it work with :with-broken-links mark, but that
might overrule what is in an #+OPTIONS line.

So, my question is how do I get the value of what :with-broken-links should
be that has the right prececedence, i.e. OPTIONS
> org-export-with-broken-links, during the export?

Thanks,

John

---
Professor John Kitchin
Doherty Hall A207F
Department of Chemical Engineering
Carnegie Mellon University
Pittsburgh, PA 15213
412-268-7803
@johnkitchin
http://kitchingroup.cheme.cmu.edu

Re: [O] [PATCH] Add option to automatically align tags in agenda view

[Kyle Meyer]

> Kyle Meyer  writes:

>>> I don't know if this still technically qualifies as a tinychange.  I've
>>> sent the email to request the CA form just in case.
>>
>> I don't know either.  How about I apply your *.el changes, and we can
>> update ORG-NEWS once your assignment comes through?

On second thought (and counting lines with new content), I think the
entire patch is OK as a tinychange.  Applied to master with minor
formatting tweaks to the log message and NEWS entry.

I've added you to http://orgmode.org/worg/org-contribute.html under the
"processing assignment" section.

Thanks.

-- 
Kyle

[O] Table columns not aligning when width set

[William Denton]

I noticed this last week, but I'm on vacation.  I'm compiling and running Org 
and Emacs from source, and have been keeping up to date, but the problem's been 
there for a while.  For Org, I'm on the master branch, not tables, and running 
"make update" to update.


In the example below, the <40> and <10> widths are not respected.  If you hit 
C-c C-C on the STARTUP line, first one things goes wrong and then another, and 
you can toggle back and forth.


Bill

# --

#+TITLE: Table column problem
#+STARTUP: align

| Forty| Ten  |
| <40> | <10> |
|--+--|
| This cell has more than forty characters in it, but it won't align | Under.   
|
| This cell has under forty characters.| More than ten over here. |

# --

--
William Denton :: Toronto, Canada   ---   Listening to Art: 
https://listeningtoart.org/
https://www.miskatonic.org/ ---   GHG.EARTH: http://ghg.earth/
Caveat lector.  ---   STAPLR: http://staplr.org/

Re: [O] [PATCH] Add option to automatically align tags in agenda view

[Adam Porter]

Kyle Meyer  writes:

>From ea3007a8b35d727f71860bd7697808f90d5e1e66 Mon Sep 17 00:00:00 2001
From: Adam Porter 
Date: Mon, 7 Aug 2017 08:50:26 -0500
Subject: [PATCH] org-agenda.el: Add option to automatically align tags in
 agenda

* lisp/org-agenda.el:
  (org-agenda-tags-column): Add 'auto setting.
  (org-agenda-align-tags): Handle automatic alignment.

* etc/ORG-NEWS: Document this new setting.

TINYCHANGE
---
 etc/ORG-NEWS   |  4 
 lisp/org-agenda.el | 24 ++--
 2 files changed, 22 insertions(+), 6 deletions(-)

diff --git a/etc/ORG-NEWS b/etc/ORG-NEWS
index 6361923..0aa0844 100644
--- a/etc/ORG-NEWS
+++ b/etc/ORG-NEWS
@@ -112,6 +112,10 @@ docstrings.
  New variable : ~org-deadline-past-days~
 See docstring for details.
  Binding C-c C-x < for ~org-agenda-set-restriction-lock-from-agenda~
+ New auto-align default setting for =org-agenda-tags-column=
+
+=org-agenda-tags-column= can now be set to ='auto=, which will automatically align tags to the right edge of the window.  This is now the default setting.
+
 *** New value for ~org-publish-sitemap-sort-folders~
 
 The new ~ignore~ value effectively allows toggling inclusion of
diff --git a/lisp/org-agenda.el b/lisp/org-agenda.el
index c8097de..93148d0 100644
--- a/lisp/org-agenda.el
+++ b/lisp/org-agenda.el
@@ -1886,13 +1886,21 @@ When this is the symbol `prefix', only remove tags when
 (defvaralias 'org-agenda-remove-tags-when-in-prefix
   'org-agenda-remove-tags)
 
-(defcustom org-agenda-tags-column -80
+(defcustom org-agenda-tags-column 'auto
   "Shift tags in agenda items to this column.
-If this number is positive, it specifies the column.  If it is negative,
-it means that the tags should be flushright to that column.  For example,
--80 works well for a normal 80 character screen."
+If set to `auto', tags will be automatically aligned to the right
+edge of the window.
+
+If set to a positive number, tags will be left-aligned to that
+column.  If set to a negative number, tags will be right-aligned
+to that column.  For example, -80 works well for a normal 80
+character screen."
   :group 'org-agenda-line-format
-  :type 'integer)
+  :type '(choice
+	  (const :tag "Automatically align to right edge of window" auto)
+	  (integer :tag "Specific column" -80))
+  :package-version '(Org . "9.1")
+  :version "26.1")
 
 (defvaralias 'org-agenda-align-tags-to-column 'org-agenda-tags-column)
 
@@ -8959,7 +8967,11 @@ If FORCE-TAGS is non nil, the car of it returns the new tags."
 
 (defun org-agenda-align-tags ( line)
   "Align all tags in agenda items to `org-agenda-tags-column'."
-  (let ((inhibit-read-only t) l c)
+  (let ((inhibit-read-only t)
+	(org-agenda-tags-column (if (eq 'auto org-agenda-tags-column)
+(- (window-text-width))
+  org-agenda-tags-column))
+	l c)
 (save-excursion
   (goto-char (if line (point-at-bol) (point-min)))
   (while (re-search-forward "\\([ \t]+\\)\\(:[[:alnum:]_@#%:]+:\\)[ \t]*$"
-- 
2.7.4


> As you can see in the diffs above, master-only changes are using 26.1
> for :version.  Assuming Org 9.0.* ships with Emacs 26.1, these will be
> wrong, but they can be updated all together once 26.2 is released.

I have been getting my numbers mixed up.  :)  Fixed.

> Thanks.  Did you forget to attach the patch?

Yes.  :(

But not this time!

>> I don't know if this still technically qualifies as a tinychange.  I've
>> sent the email to request the CA form just in case.
>
> I don't know either.  How about I apply your *.el changes, and we can
> update ORG-NEWS once your assignment comes through?

Sure.  Thanks for your patience.  Please let me know if any other
changes are needed.

Re: [O] [PATCH] Add option to automatically align tags in agenda view

[Kyle Meyer]

Kyle Meyer  writes:

> As you can see in the diffs above, master-only changes are using 26.1
> for :version.  Assuming Org 9.0.* ships with Emacs 26.1, these will be
> wrong, but they can be updated all together once 26.2 is released.
   
  Doh, 26.1
-- 
Kyle

Re: [O] [PATCH] Add option to automatically align tags in agenda view

[Kyle Meyer]

Adam Porter  writes:

> Kyle Meyer  writes:

[...]

>> Since you're changing the default value, shouldn't you add appropriate
>> values for the :version and :package-version keywords?
>
> Thanks, I didn't know about these.  I set :package-version to 9.1, since
> that should be the next Org release, I guess.

Yep, master-only changes are using 9.1 for :package-version

$ git log -u -G":package-version" maint..master

> I set :version to 26.3 since I guess that will be the next Emacs
> release, although I don't know if it will include Org 9.1.  Let me
> know if these need to be changed.

As you can see in the diffs above, master-only changes are using 26.1
for :version.  Assuming Org 9.0.* ships with Emacs 26.1, these will be
wrong, but they can be updated all together once 26.2 is released.

>> It'd be good to mention this change in ORG-NEWS as well.
>
> I should have thought of that.  Done.

Thanks.  Did you forget to attach the patch?

> I don't know if this still technically qualifies as a tinychange.  I've
> sent the email to request the CA form just in case.

I don't know either.  How about I apply your *.el changes, and we can
update ORG-NEWS once your assignment comes through?

-- 
Kyle

Re: [O] verbatim =[[link]]= and code ~[[link]]~ render as links

[Kaushal Modi]

On Tue, Aug 8, 2017, 1:02 PM Adam Porter  wrote:

>
>
> Well, here's what I've noticed:
>

My observations have been the same. I strongly believe that GitHub needs to
fix their parsing of Org verbatim/code text.

Here's another similar problem with GitHub rendering Org verbatim, in
tables:
https://github.com/kaushalmodi/ox-hugo/blob/master/README.org#formatting

Note the ==monospace== text in the table.

So maybe Wolfram is right here, and the the problems are with the way
> the ...[=description=]] links are rendered in Emacs and on GitHub.
>

Yup. Another reason to believe so is that

[[https://www.example.com][=description=]]

is equivalent to

[`description`](https://www.example.com)

in Markdown, and GitHub renders the Markdown version fine.

Also, below won't be rendered as a link :)

`[description](https://www.example.com)`

> --

Kaushal Modi

[O] Small code fragment to make zone-mode play well with org

[Marc Ihm]

Hi,

with the fragment below in my startup-file, zone-mode handles hidden 
text correctly (does not reveal it) and thus plays well with orgmode.


(Of course the correct way to handle this would be to create a proper 
patch for zone.el instead of fixing this locally; but I am sending it 
here anyway: maybe someone has commit-rights to emacs core itself ...)



best regards
Marc Ihm


(advice-add
 'zone :around
 (lambda (orig-fun  args) (interactive)
   (let (result text name)
 (when (string= major-mode "org-mode")
   (setq text (org-copy-visible (window-start) (window-end)))
   (setq name (generate-new-buffer-name (buffer-name)))
   (switch-to-buffer (get-buffer-create name))
   (erase-buffer)
   (insert text))
 (setq result (apply orig-fun args))
 (if name (kill-buffer name))
 result)))

Re: [O] verbatim =[[link]]= and code ~[[link]]~ render as links

[Adam Porter]

Kaushal Modi  writes:

> Are you referring to:
>
> [[https://www.example.com][=verbatim link descr=]]
>
> ?

Well, here's what I've noticed:

+ [[https://www.example.com][=verbatim link descr=]]
  - Renders in the Emacs buffer as a link, colored as a link rather than
a code block, with visible =description=.
  - Exports to HTML as ..., which looks fine
  - Renders on GitHub as =description=, which is incorrect
  
+ =[[https://www.example.com][verbatim link descr]]=
  - Renders in the Emacs buffer as a link with the same color as other
=code= blocks.
  - Exports to HTML as [[https://www.example.com][verbatim link
descr]], which I guess makes sense.
  - Renders on GitHub as [[https://www.example.com][verbatim link
descr]], which is consistent.

So maybe Wolfram is right here, and the the problems are with the way
the ...[=description=]] links are rendered in Emacs and on GitHub.

Re: [O] [PATCH] Add option to automatically align tags in agenda view

[Adam Porter]

Kyle Meyer  writes:

>> (org-agenda-align-tags): Handle automatic alignment
>> (org-agenda-tags-column): Add 'auto setting
>
> You're missing the file name in the entries above.  Also, the entries
> should end in a period.

Oops, fixed.

> Since you're changing the default value, shouldn't you add appropriate
> values for the :version and :package-version keywords?

Thanks, I didn't know about these.  I set :package-version to 9.1, since
that should be the next Org release, I guess.  I set :version to 26.3
since I guess that will be the next Emacs release, although I don't know
if it will include Org 9.1.  Let me know if these need to be changed.

> It'd be good to mention this change in ORG-NEWS as well.

I should have thought of that.  Done.

I don't know if this still technically qualifies as a tinychange.  I've
sent the email to request the CA form just in case.

Thanks.

Re: [O] verbatim =[[link]]= and code ~[[link]]~ render as links

[Kaushal Modi]

On Tue, Aug 8, 2017 at 11:07 AM Adam Porter  wrote:

> Wolfram Volpi  writes:
>
> > org-mode renders links in verbatim and code as links:
> >
> > verbatim: =[[link]]=
> >
> > code: ~[[link]]~
> >
> > They should be rendered as plain text.
>
> Hi Wolfram,
>
> Why do you think they should be rendered as plain text instead of as
> links?  I use verbatim/code-styled links often in documentation, and I
> would not want them to be displayed as plain-text; I want them to be
> rendered as links, because they are.  :)
>

 Are you referring to:

[[https://www.example.com][=verbatim link descr=]]

?

Because I use that all the time to show links to code like .el files.

Regarding Wolfram's suggestion.. it makes sense that if someone wants to
show the Org link representation verbatim, it should be possible.


-- 

Kaushal Modi

Re: [O] emacs-orgmode "Archives Search String" search box is broken.

[Adam Porter]

Wolfram Volpi  writes:

> From http://lists.gnu.org/archive/html/emacs-orgmode/, the emacs-orgmode 
> "Archives Search String".
> The search box gets results that have nothing to do with the search terms I 
> entered.
>
> hesiii said the same thing on
> https://www.reddit.com/r/orgmode/comments/69omn5/how_to_search_mailing_list_archive/

As far as I know, this is a limitation of the mailing list software.  It
affects all GNU-hosted lists, not just the Org list, so you should
probably talk to the FSF list admins.

Re: [O] ox-taskjuggler on MELPA useful despite org-plus-contrib

[Adam Porter]

Nicolas Goaziou  writes:

>> At least until the underlying problem with org-plus-contrib is
>> resolved.
>
> What exactly is the underlying problem?

FWIW I have been using org-plus-contrib for a while now, and I haven't
had any problems with my customizations.

Re: [O] source block breaks when code looks like heading

[Adam Porter]

bruce robertson  writes:

> How would the source for the math then work?

If you edit the code-block with C-c ', the escape characters will be
handled automatically.

Re: [O] verbatim =[[link]]= and code ~[[link]]~ render as links

[Adam Porter]

Wolfram Volpi  writes:

> org-mode renders links in verbatim and code as links:
>
> verbatim: =[[link]]=
>
> code: ~[[link]]~
>
> They should be rendered as plain text.

Hi Wolfram,

Why do you think they should be rendered as plain text instead of as
links?  I use verbatim/code-styled links often in documentation, and I
would not want them to be displayed as plain-text; I want them to be
rendered as links, because they are.  :)

[O] verbatim =[[link]]= and code ~[[link]]~ render as links

[Wolfram Volpi]

org-mode renders links in verbatim and code as links:


verbatim: =[[link]]=

code: ~[[link]]~



They should be rendered as plain text.


I am running org-version 9.0.9.


 System Info :computer:

- OS: gnu/linux

- Emacs: 25.2.1

- Spacemacs: 0.200.9

- Spacemacs branch: master (rev. 8e1af145)

- Graphic display: t

- Distribution: spacemacs

- Editing style: vim

- Completion: ivy

- Layers:

```elisp

(ivy evil-snipe emacs-lisp org spell-checking)

```

- System configuration features: XPM JPEG TIFF GIF PNG RSVG IMAGEMAGICK SOUND 
DBUS GCONF GSETTINGS NOTIFY ACL LIBSELINUX GNUTLS LIBXML2 FREETYPE M17N_FLT 
LIBOTF XFT ZLIB TOOLKIT_SCROLL_BARS GTK3 X11 MODULES XWIDGETS



Wolfram Volpi

[O] emacs-orgmode "Archives Search String" search box is broken.

[Wolfram Volpi]

>From http://lists.gnu.org/archive/html/emacs-orgmode/, the emacs-orgmode 
>"Archives Search String".
The search box gets results that have nothing to do with the search terms I 
entered.

hesiii said the same thing on 
https://www.reddit.com/r/orgmode/comments/69omn5/how_to_search_mailing_list_archive/

Re: [O] source block breaks when code looks like heading

[bruce robertson]

How would the source for the math then work?

On Tue, Aug 8, 2017 at 12:45 AM Nicolas Goaziou 
wrote:

> Hello,
>
> bruce robertson  writes:
>
> > multi-line comments or expressions appearing to be headings break block.
> >
> > * top
> >
> > #+begin_src php
> > /*
> > *do not prepend a space to 'do'
> > */
> > b = 2
> > *3; // do not prepend a space to '3'
> > #+end_src
>
> You need to prepend a comma before the asterisks. See (info "(org)Literal
> examples").
>
> Regards,
>
> --
> Nicolas Goaziou
>

Re: [O] ox-taskjuggler on MELPA useful despite org-plus-contrib

[Nicolas Goaziou]

Hello,

Simon Guest  writes:

> Well, almost as soon as I started on that, I see some issues around mixing
> old/new org-mode functionality, so this seems like a not-so-good idea after
> all.
>
> In particular, ox-taskjuggler is using the very new org-duration
> library.

You could use "ox-taskjuggler" from maint.

> I'll think of another approach, not using MELPA.

I suggest to use GNU ELPA instead.

> At least until the underlying problem with org-plus-contrib is
> resolved.

What exactly is the underlying problem?

Regards,

-- 
Nicolas Goaziou

Re: [O] source block breaks when code looks like heading

[Nicolas Goaziou]

Hello,

bruce robertson  writes:

> multi-line comments or expressions appearing to be headings break block.
>
> * top
>
> #+begin_src php
> /*
> *do not prepend a space to 'do'
> */
> b = 2
> *3; // do not prepend a space to '3'
> #+end_src

You need to prepend a comma before the asterisks. See (info "(org)Literal
examples").

Regards,

-- 
Nicolas Goaziou

Re: [O] clock start time is gone

[Nicolas Goaziou]

Hello,

Samuel Wales  writes:

> On 8/7/17, Nicolas Goaziou  wrote:
>> I'm not sure about the steps required to reproduce your issue. What do
>> you do on the same mwe? Clock in
>>
>>   "* clock in here, then sort below, then try to clock out here"
>>
>> then sort at
>>
>>   "*** sort here by alpha"
>>
>> then clock out?

Then I cannot reproduce it. Either from maint or master branch.

Regards,

-- 
Nicolas Goaziou