[O] Problem with Org-mobile

[Steve Prud'Homme]

Hi,
this is my .emacs setting for org-mobile file :





*(setq org-directory "H:\\Dropbox\\PROJETS\\PERSONNEL\\Notes\\org");; Set
to the name of the file where new notes will be stored(setq
org-mobile-inbox-for-pull
"H:\\Dropbox\\PROJETS\\PERSONNEL\\Notes\\org\\flagged.org
");; Set to /MobileOrg.(setq org-mobile-directory
"H:\\Dropbox\\Applications\\MobileOrg")*

When I do a org-mobile-push everything works fine, the file are staged.
When I go in the mobile-org App on my phone I sync, nothing append, no file
is showing.

I have Windows 7 Utilmage 64 bits, GNU Emacs 25.2.1 (x86_64-w64-mingw32),
org-mode 9.0.7, gnuwin v0.6.3.1, md5sums v1.2 and
gnuwin32-coreutils.install v5.3.0

This is my checksum file



*f9e61c780722c7e3655509c1b318d221  index.org
68b329da9893e34099c7d8ad5cb9c940  mobileorg.org
968e7b73c1aeb1eadc33b2a8c05d1bf9  agendas.org
*

I don't know what is the problem exacly...


-- 
Posté par Steve Prud'Homme
[image: FSF Associate Member]

Re: [O] newbye questions

[Eric Abrahamsen]

François Patte  writes:

> Bonjour,
>
> Ijust discovered org-mode for emacs and I want to explore the
> capabilities of this mode for LaTeX documents.
>
> I have a few preliminary questions:
>
> 1- I installed org-mode from ELPA and I get a warning message when I
> open a *.org file:
>
> Eager macro-expansion failure: (error "Autoloading failed to define
> function nnir-article-group")
>
> What does it mean and how to get rid of this message.

That's a macro from Gnus, the mail/news client. I'm not quite sure why
it would be getting triggered from Org. Would you run
`toggle-debug-on-error', and trigger the warning again?

Eric

Re: [O] Moving and resetting attachments

[Eric Abrahamsen]

Nicolas Goaziou  writes:

> Hello,
>
> Eric Abrahamsen  writes:
>
>> What I meant was, first ask the user for a directory, then cycle through
>> the files and ask whether to move each file to that directory. The user
>> wouldn't specify the directory itself for each file. And with
>> `map-y-or-n-p', the user can just hit "!" to take care of all files.
>>
>> Am I misunderstanding your concern? The only time the ID attachment
>> directory scheme (which is indeed opaque) would come into play is when
>> the command was called with a prefix argument -- ie, when removing a
>> custom directory, and reverting to the automatic directory. In that
>> case, the directory would be automatically derived, and the user would
>> simply be presented with the choice to move each file there, or not.
>
> When asking for each file if it should be moved or not, you can end up
> with files in both the old and the new directory. My concern is that,
> when the old directory is a default ID directory, there is no simple way
> to get the files back. So, I think we should automatically move files in
> this case.
>
> I also agree with your special case described above.

Okay, makes sense. I hope we haven't totally scared off Florian...

Florian, are you interested in doing another version of the patch?

Eric

Re: [O] exporting markdown with tables

[Peter Davis]

Thanks to all for the responses here. They have opened my eyes to new
org features I can use in other ways.

For now, I think my solution to the table export question will be just
to keep everything in org mode and to heck with Editorial and Markdown.

Thanks!

-pd



-- 
  Peter Davis
  www.techcurmudgeon.com

Re: [O] Warning (emacs): Please update your Org Protocol handler to deal with new-style links.

[Samuel Wales]

On 6/4/17, Nicolas Goaziou  wrote:
>> does this mean org-capture extension [the one with the unicorn icon in
>> firefox] needs to be changed?
>
> Probably.

thank you.  i don't mind the warnings, unless they mean that backward
compatibility will go away and then org-capture will break again for
me.  i have been enjoying its working very much.  [i rely on it as i
cannot use keyboard much of the time.[

Re: [O] newbye questions

[Nick Dokos]

François Patte  writes:

> 2- I looked at some tutorials (for instance this one:
> http://hiko-seijuro.developpez.com/articles/orgtutorial/)
>
> It is said at the early beginning for a TODO list, that if you hit C-c
> C-t TODO turns into DONE (that's right) and that a timestamp is
> automatically added:
> CLOSED: [date for closing]
>
> I cannot get this behaviour I googled and find some list code to add
> to my .emacs file, but this does not work
>

(setq org-log-done 'time)

See the section "Closing items" in the Org manual.

-- 
Nick

Re: [O] Warning (emacs): Please update your Org Protocol handler to deal with new-style links.

[Nicolas Goaziou]

Samuel Wales  writes:

> On 6/3/17, Nicolas Goaziou  wrote:
>> See ORG-NEWS, for release 9.0. It is easy to get rid of this warning.
>
> where does one make that change?  i don't know what a handler function
> is.  all i define is a capture template.
>
> does this mean org-capture extension [the one with the unicorn icon in
> firefox] needs to be changed?

Probably.

Regards,

Re: [O] exporting markdown with tables

[Charles C. Berry]

On Sun, 4 Jun 2017, Vicente Vera wrote:


Cool, you're welcome. It is not the most convenient solution, but
keeping your tables in Editorial Markdown syntax should work:

#+BEGIN_EXPORT md
Cat | Fur   |
--- | ---   |
A   | A lot |
B   | None  |
#+END_EXPORT



Except that the above is not recognized as a table, so all the nifty tools 
for table editing are lost.


IMO, a better solution is to create a filter for table-row that replaces 
the leading vertical with a space (or nothing) and bind that function to 
`org-export-filter-table-row-functions'. See


(info "(org) Advanced configuration")


---

However, those intimidated by filters can keep tables in org src blocks 
and convert them on export using a :post argument to clean the leading 
verticals.  That way the tables can be edited as usual via 
org-edit-src-code:


#+name: strip-leading-vertical
#+BEGIN_SRC emacs-lisp
(replace-regexp-in-string "^|" " " *this*)
#+END_SRC


#+header: :results replace :exports results
#+header: :post strip-leading-vertical() :wrap export md
#+BEGIN_SRC org
  | a | b |
  |---+---|
  | 1 | 2 |
  | 3 | 4 |
#+END_SRC

#+RESULTS:
#+BEGIN_export md
  a | b |
 ---+---|
  1 | 2 |
  3 | 4 |
#+END_export

A call to `(require 'ob-org)' or suitable customization is needed to 
enable the org src block to execute.


HTH,

Chuck

Re: [O] Warning (emacs): Please update your Org Protocol handler to deal with new-style links.

[Samuel Wales]

On 6/3/17, Nicolas Goaziou  wrote:
> See ORG-NEWS, for release 9.0. It is easy to get rid of this warning.

where does one make that change?  i don't know what a handler function
is.  all i define is a capture template.

does this mean org-capture extension [the one with the unicorn icon in
firefox] needs to be changed?

or is it on the lisp side and my org-protocol version is out of date?

-- 
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] exporting markdown with tables

[Vicente Vera]

Cool, you're welcome. It is not the most convenient solution, but
keeping your tables in Editorial Markdown syntax should work:

#+BEGIN_EXPORT md
Cat | Fur   |
--- | ---   |
A   | A lot |
B   | None  |
#+END_EXPORT

2017-06-03 16:46 GMT+00:00 Peter Davis :
> Thanks, Vincente.
>
> I'm specifically aiming at the Markdown syntax supported by the Editorial
> app, which does include markup for tables. Unfortunately, it looks like
> Editorial's Markdown doesn't use the initial '|', so simply exporting the
> org markup won't work without some editing.
>
> Thanks!
> -pd
>
> On Sat, Jun 3, 2017, at 12:31 PM, Vicente Vera wrote:
>> There are several Markdown "forks" which have different sets of features.
>>
>> AFAIK the markdown exporter in Org is based upon John Gruber's
>> Markdown, which does not include a syntax for tables. Thus all tables
>> in Org documents get exported as HTML.
>>
>> A workaround is to wrap your Org tables as:
>>
>> #+BEGIN_EXPORT md
>> | Name   | Years |
>> | Edward |44 |
>> | Sylvia |45 |
>> #+END_EXPORT
>>
>> On export to Markdown the tables will be kept unmodified as Org syntax.
>>
>> It is important that you know which flavor of Markdown you're
>> targeting, because not all versions accept tables in Org syntax.
>> Pandoc's Markdown have a similar syntax for "pipe tables". However,
>> you may type all tables in any syntax accepted by your Markdown
>> version and keep them wrapped in #+BEGIN_EXPORT tags.
>>
>> 2017-06-03 13:41 GMT+00:00 Peter Davis :
>> >
>> > I'd like to be able to move easily between org-mode and the IOS app
>> > Editorial, which is mainly based around markdown syntax. I can
>> > easily export markdown from org-mode, but the tables seems to come
>> > through as straight HTML, as opposed to markdown's table
>> > syntax. This makes it more difficult to edit the resulting files.
>> >
>> > Is there a way to get org to export to markdown using md's table syntax?
>> >
>> > (FWIW, I tried using pandoc, but this just removed the table syntax
>> > altogether, so an entire table would just run together into a
>> > paragraph of gibberish.)
>> >
>> > Thanks,
>> > -pd
>> >
>> >
>
>
> --
>   Peter Davis
>   www.techcurmudgeon.com
>

Re: [O] truncate-lines for org tables, visual-line-mode for rest?

[Michael Brand]

Hi all

On Mon, Jan 26, 2015 at 9:24 PM, Eric S Fraga  wrote:

> On Monday, 26 Jan 2015 at 21:43, Vladimir Alexiev wrote:

>> I use visual-line-mode to wrap long lines on display.
>> But for org tables, wrapping makes the display very confused.
>> Is it possible to have truncate-lines ONLY for lines that represent tables?

> I have the same issue.  I do have visual-line-mode bound to a key so I
> can toggle this on and off easily but it would definitely be nice if I
> didn't have to do anything...  however, I think it will be difficult to
> automate this.

Carsten made an Emacs feature request for this here
http://debbugs.gnu.org/cgi/bugreport.cgi?bug=5018

As I am also very interested in this I commented there now. Please
help me by showing your interest there too.

Michael

Re: [O] org to static site?

[Scott Randby]

On 05/31/2017 11:00 AM, Matt Price wrote:
> I'm trying to wean myself off of Wordpress for next year's teaching
> websites, and am wondering what solutions other people are using for
> turning a collection of org pages and/or subtrees into a static html
> site. I am leaning towards Hugo but honestly not for any sensible
> reason; I've seen other people use Jekyll, though the fact that Github
> doesn't support direct conversion from org-mode removes some of Jekyll's
> appeal; and I know there are a number of other solutions too. 
> 
> So, I would love to hear what you all recommend.

Maybe this is too primitive, but I keep all the content in one Org file
and export the text under each top-level headline as a single HTML page.
I use some simple macros if I need to export more than one top-level
headline. I keep the CSS code in a separate file. Keeping all the
content in one file makes it really easy to add new pages and edit old
pages. I use a preamble for site navigation.

Scott Randby

Re: [O] exporting markdown with tables

[Joost Kremers]

On Sat, Jun 03 2017, Peter Davis wrote:
(FWIW, I tried using pandoc, but this just removed the table 
syntax altogether, so an entire table would just run together 
into a

paragraph of gibberish.)


You need a somewhat recent version of Pandoc for Org tables to be 
handled correctly (some distros still ship a very outdated 
version; latest is 1.19), and not all features are supported. So 
yeah, it's not necessarily the best option...



--
Joost Kremers
Life has its moments

[O] newbye questions

[François Patte]

Bonjour,

Ijust discovered org-mode for emacs and I want to explore the
capabilities of this mode for LaTeX documents.

I have a few preliminary questions:

1- I installed org-mode from ELPA and I get a warning message when I
open a *.org file:

Eager macro-expansion failure: (error "Autoloading failed to define
function nnir-article-group")

What does it mean and how to get rid of this message.

2- I looked at some tutorials (for instance this one:
http://hiko-seijuro.developpez.com/articles/orgtutorial/)

It is said at the early beginning for a TODO list, that if you hit C-c
C-t TODO turns into DONE (that's right) and that a timestamp is
automatically added:
CLOSED: [date for closing]

I cannot get this behaviour I googled and find some list code to add
to my .emacs file, but this does not work

What can I do?

Thank you.

-- 
François Patte
UFR de mathématiques et informatique
Laboratoire CNRS MAP5, UMR 8145
Université Paris Descartes
45, rue des Saints Pères
F-75270 Paris Cedex 06
Tél. +33 (0)6 7892 5822
http://www.math-info.univ-paris5.fr/~patte



signature.asc
Description: OpenPGP digital signature

Re: [O] Bug: buffer local variables handled wrong [9.0.5 (release_9.0.5-497-g5bc540 @ /home/hs/.emacs.d/lib/org-mode/lisp/)]

[Stefan-W. Hahn]

Mail von Nicolas Goaziou, Sun, 04 Jun 2017 at 11:35:34 +0200:

Hello,

> "Stefan-W. Hahn"  writes:
> 
> > What I don't understand is, if I expand the pcase with (macrostep-expand) I
> > get the following:
> >
> > ,
> > | (let (res)
> > | (dolist (pair (buffer-local-variables))
> > |   (if
> > |   (consp pair)
> > |   (let*
> > |   ((x
> > | (car pair))
> > |(x
> > | (cdr pair)))
> > | (let
> > | ((val x)
> > |  (var x))
> > |   (push
> > |(list 'set var val)
> > |res)))
> > | nil))
> > | res)
> > `
> >
> > And this is obviously wrong.
> 
> This is not obviously wrong. You may be thinking that both `x' symbols
> are the same, but they are not. E.g.,
> 
>   (let ((s1 (make-symbol "x"))
> (s2 (make-symbol "x")))
> (list (list s1 s2) (eq s1 s2)))
> 
>   =>
> 
>   ((x x) nil)

This I understand, but cannot see it in the macrostep-expanded code.
I will try learn more to understand this. 

So it is obvoius now that you are a lisp magician of 8th grade. :-)

Thanks and kind regards,
Stefan

-- 
Stefan-W. Hahn  It is easy to make things.
It is hard to make things simple.

Re: [O] exporting LaTeX to ODT with custom symbols

[Nicolas Goaziou]

Hello,

ed...@openmail.cc writes:

> I'm having some issues when exporting to ODT, and I would like to know
> if someone can help me. I tried my best to describe the problem in the
> the attached tmp.org. I also attach a symbols.tex which has my custom
> symbols.

You may want to try tweaking `org-preview-latex-process-alist'. There is
possibly room for improvement in the UI here.

Regards,

-- 
Nicolas Goaziou

Re: [O] Bug: buffer local variables handled wrong [9.0.5 (release_9.0.5-497-g5bc540 @ /home/hs/.emacs.d/lib/org-mode/lisp/)]

[Nicolas Goaziou]

"Stefan-W. Hahn"  writes:

> What I don't understand is, if I expand the pcase with (macrostep-expand) I
> get the following:
>
> ,
> | (let (res)
> | (dolist (pair (buffer-local-variables))
> |   (if
> |   (consp pair)
> |   (let*
> |   ((x
> | (car pair))
> |(x
> | (cdr pair)))
> | (let
> | ((val x)
> |  (var x))
> |   (push
> |(list 'set var val)
> |res)))
> | nil))
> | res)
> `
>
> And this is obviously wrong.

This is not obviously wrong. You may be thinking that both `x' symbols
are the same, but they are not. E.g.,

  (let ((s1 (make-symbol "x"))
(s2 (make-symbol "x")))
(list (list s1 s2) (eq s1 s2)))

  =>

  ((x x) nil)

Regards,

Re: [O] Bug: buffer local variables handled wrong [9.0.5 (release_9.0.5-497-g5bc540 @ /home/hs/.emacs.d/lib/org-mode/lisp/)]

[Stefan-W. Hahn]

Mail von Nicolas Goaziou, Sun, 04 Jun 2017 at 10:24:57 +0200:

Hello,

> "Stefan-W. Hahn"  writes:
> 
> > I looked at it, but sorry, I think this also is not right, it expands to:
> >
> > Both looking wrong for me. Sorry.
> 
> What do you think is wrong?
> 
> In particular
> 
>   (let (res)
> (dolist (pair (buffer-local-variables))
>   (pcase pair
> (`(,var . ,val)
>  (push (list 'set var val) res
> res)
> 
> expands to
> 
>   ((set flyspell-word-cache-result _)
>(set flyspell-word-cache-end -1)
>(set undo-auto--last-boundary-cause (2 #))
>(set syntax-ppss-last (1 0 nil nil nil nil nil 0 nil nil nil))
>(set syntax-propertize--done 139)
>(set flyspell-changes nil)
>(set deactivate-mark nil)
>(set flyspell-pre-point 139)
>(set auto-revert-notify-modified-p nil)
>...
>)
> 
> which looks correct.

Obviously you are right, I get the ame result when evaluating it.

What I don't understand is, if I expand the pcase with (macrostep-expand) I
get the following:

,
| (let (res)
| (dolist (pair (buffer-local-variables))
|   (if
|   (consp pair)
|   (let*
|   ((x
| (car pair))
|(x
| (cdr pair)))
| (let
| ((val x)
|  (var x))
|   (push
|(list 'set var val)
|res)))
| nil))
| res)
`

And this is obviously wrong.

With kind regards,
Stefan

-- 
Stefan-W. Hahn  It is easy to make things.
It is hard to make things simple.

Re: [O] Bug: buffer local variables handled wrong [9.0.5 (release_9.0.5-497-g5bc540 @ /home/hs/.emacs.d/lib/org-mode/lisp/)]

[Nicolas Goaziou]

"Stefan-W. Hahn"  writes:

> I looked at it, but sorry, I think this also is not right, it expands to:
>
> ,
> | (defun org-agenda-mode ()
> | ...
> |(mapc #'make-local-variable org-agenda-local-vars)
> |(dolist (elem save)
> |  (if
> |  (consp elem)
> |  (let*
> |  ((x
> |(car elem))
> |   (x
> |(cdr elem)))
> |(let
> |((val x)
> | (var x))
> |  (when
> |  (and val
> |   (memq var org-agenda-local-vars))
> |(set var val
> |nil)))
> |  (setq-local org-agenda-this-buffer-is-sticky t))
> | (org-agenda-sticky
> `
>
> and the second one:
>
> ,
> | (defun org-clone-local-variables (from-buffer  regexp)
> | ...
> |   (dolist (pair (buffer-local-variables from-buffer))
> | (if
> | (consp pair)
> | (let*
> | ((x
> |   (car pair))
> |  (x
> |   (cdr pair)))
> |   (if
> |   (consp x)
> |   (let*
> |   ((x
> | (cdr x)))
> | (if
> | (null x)
> | (let
> | ((name x))
> |   (when
> |   (and
> |(not
> | (memq name org-unique-local-variables))
> |(or
> | (null regexp)
> | (string-match-p regexp
> | (symbol-name name
> | (set
> |  (make-local-variable name)
> |  (cdr pair
> |   nil))
> | nil))
> |   nil)))
> `
>
> Both looking wrong for me. Sorry.

What do you think is wrong?

In particular

  (let (res)
(dolist (pair (buffer-local-variables))
  (pcase pair
(`(,var . ,val)
 (push (list 'set var val) res
res)

expands to

  ((set flyspell-word-cache-result _)
   (set flyspell-word-cache-end -1)
   (set undo-auto--last-boundary-cause (2 #))
   (set syntax-ppss-last (1 0 nil nil nil nil nil 0 nil nil nil))
   (set syntax-propertize--done 139)
   (set flyspell-changes nil)
   (set deactivate-mark nil)
   (set flyspell-pre-point 139)
   (set auto-revert-notify-modified-p nil)
   ...
   )

which looks correct.

Regards,

Re: [O] Bug: buffer local variables handled wrong [9.0.5 (release_9.0.5-497-g5bc540 @ /home/hs/.emacs.d/lib/org-mode/lisp/)]

[Stefan-W. Hahn]

Mail von Nicolas Goaziou, Sun, 04 Jun 2017 at 09:19:09 +0200:

Good morning again,

> Hello,
> 
> "Stefan-W. Hahn"  writes:
> 
> > For me both cases don't look correct or do I missinterpret something?
> 
> No, you're right. I fixed it. Thank you.

I looked at it, but sorry, I think this also is not right, it expands to:

,
| (defun org-agenda-mode ()
| ...
|  (mapc #'make-local-variable org-agenda-local-vars)
|  (dolist (elem save)
|(if
|(consp elem)
|(let*
|((x
|  (car elem))
| (x
|  (cdr elem)))
|  (let
|  ((val x)
|   (var x))
|(when
|(and val
| (memq var org-agenda-local-vars))
|  (set var val
|  nil)))
|(setq-local org-agenda-this-buffer-is-sticky t))
|   (org-agenda-sticky
`

and the second one:

,
| (defun org-clone-local-variables (from-buffer  regexp)
| ...
|   (dolist (pair (buffer-local-variables from-buffer))
| (if
|   (consp pair)
|   (let*
|   ((x
| (car pair))
|(x
| (cdr pair)))
| (if
| (consp x)
| (let*
| ((x
|   (cdr x)))
|   (if
|   (null x)
|   (let
|   ((name x))
| (when
| (and
|  (not
|   (memq name org-unique-local-variables))
|  (or
|   (null regexp)
|   (string-match-p regexp
|   (symbol-name name
|   (set
|(make-local-variable name)
|(cdr pair
| nil))
|   nil))
|   nil)))
`

Both looking wrong for me. Sorry.

With kind regards,
Stefan

-- 
Stefan-W. Hahn  It is easy to make things.
It is hard to make things simple.

Re: [O] Moving and resetting attachments

[Nicolas Goaziou]

Hello,

Eric Abrahamsen  writes:

> What I meant was, first ask the user for a directory, then cycle through
> the files and ask whether to move each file to that directory. The user
> wouldn't specify the directory itself for each file. And with
> `map-y-or-n-p', the user can just hit "!" to take care of all files.
>
> Am I misunderstanding your concern? The only time the ID attachment
> directory scheme (which is indeed opaque) would come into play is when
> the command was called with a prefix argument -- ie, when removing a
> custom directory, and reverting to the automatic directory. In that
> case, the directory would be automatically derived, and the user would
> simply be presented with the choice to move each file there, or not.

When asking for each file if it should be moved or not, you can end up
with files in both the old and the new directory. My concern is that,
when the old directory is a default ID directory, there is no simple way
to get the files back. So, I think we should automatically move files in
this case.

I also agree with your special case described above.

Regards,

-- 
Nicolas Goaziou

Re: [O] org-wikinodes and org 9.0.7

[Nicolas Goaziou]

Hello,

Adam Sneller  writes:

> I am having trouble using org-wikinodes with the latest version of org
> (9.0.7). When I open my test.org  file, I get
> a message in the mini-buffer "Failed to add wikinodes to
> 'org-font-lock-extra-keywords'".

Fixed. Thank you.

Regards,

-- 
Nicolas Goaziou

[O] org-wikinodes and org 9.0.7

[Adam Sneller]

I am having trouble using org-wikinodes with the latest version of org (9.0.7). 
When I open my test.org  file, I get a message in the 
mini-buffer "Failed to add wikinodes to 'org-font-lock-extra-keywords'". So 
after some trial and error, I changed this line in org-wikinodes:

 (let ((m (member '(org-activate-plain-links (0 'org-link t))

to this:

 (let ((m (member '(org-activate-plain-links (0 'org-link))

And now it loads — all the CamelCase words are blue, and clicking or hitting 
C-c C-o works as well. But... org-return-follows-link does not work.  It works 
fine with all other org-links. But not org-wikinode links...

Here is what I have in my init.el file:

;;; Set default directory
(setq default-directory "~/org/")

;;; Add path to src directory
(add-to-list 'load-path "~/.emacs.d/lisp")
(add-to-list 'load-path "~/.emacs.d/lisp/org-9.0.7/lisp")
(add-to-list 'load-path "~/.emacs.d/lisp/org-9.0.7/contrib/lisp" t)

;;; Load last-opened file
(desktop-save-mode 0)

;;; Stop emacs from saving redundant backup files
(setq make-backup-files nil)

(custom-set-variables
 '(org-modules (quote (org-wikinodes)))
 '(org-return-follows-link t)
 '(org-wikinodes-scope (quote directory)))

Any ideas?

Thanks!

Re: [O] Bug: buffer local variables handled wrong [9.0.5 (release_9.0.5-497-g5bc540 @ /home/hs/.emacs.d/lib/org-mode/lisp/)]

[Nicolas Goaziou]

Hello,

"Stefan-W. Hahn"  writes:

> For me both cases don't look correct or do I missinterpret something?

No, you're right. I fixed it. Thank you.

Regards,

-- 
Nicolas Goaziou

Re: [O] Warning (emacs): Please update your Org Protocol handler to deal with new-style links.

[Nicolas Goaziou]

Hello,

Samuel Wales  writes:

> i am getting this warning:
>
> Warning (emacs): Please update your Org Protocol handler to deal with
> new-style links.
>
> is it a concern?

See ORG-NEWS, for release 9.0. It is easy to get rid of this warning.

Regards,

-- 
Nicolas Goaziou

Re: [O] Bug: buffer local variables handled wrong [9.0.5 (release_9.0.5-497-g5bc540 @ /home/hs/.emacs.d/lib/org-mode/lisp/)]

[Stefan-W. Hahn]

Mail von Nicolas Goaziou, Sat, 03 Jun 2017 at 22:46:01 +0200:

Good morning,

> >
> > This error comes from org-clone-local-variables, because there the
> > prediction for local variables is always to be a list.
> 
> Fixed. Thank you for the report and the analysis.

Thanks.

Because for me pcase is magic, I tried to understand your corretion of the
code.

To understand it I expanded the pcase form with (macrostep-expand), e.g. in
org-agenda-mode:

,
| (defun org-agenda-mode ()
| ...
|  (mapc #'make-local-variable org-agenda-local-vars)
|  (dolist (elem save)
|(if
|(consp elem)
|(let*
|((x
|  (car elem))
| (x
|  (cdr elem)))
|  (if
|  (consp x)
|  (let*
|  ((x
|(car x))
|   (x
|(cdr x)))
|(if
|(null x)
|(let
|((val x)
| (var x))
|  (when
|  (and val
|   (memq var org-agenda-local-vars))
|(set var val)))
|  nil))
|nil))
|  nil)))
|(setq-local org-agenda-this-buffer-is-sticky t))
| ...
`

for me it looks not correct, because var and val get expanded to (cdr
(cdr elem)).

Also the second one

,
| (defun org-clone-local-variables (from-buffer  regexp)
| ...
|   (dolist (pair (buffer-local-variables from-buffer))
| (if
|   (consp pair)
|   (let*
|   ((x
| (car pair))
|(x
| (cdr pair)))
| (if
| (consp x)
| (let*
| ((x
|   (cdr x)))
|   (if
|   (null x)
|   (let
|   ((name x))
| (when
| (and
|  (not
|   (memq name org-unique-local-variables))
|  (or
|   (null regexp)
|   (string-match-p regexp
|   (symbol-name name
|   (set
|(make-local-variable name)
|(cdr pair
| nil))
|   nil))
|   nil)))
`

here name get expanded to (cdr (cdr pair)).

For me both cases don't look correct or do I missinterpret something?

With kind regards,
Stefan

-- 
Stefan-W. Hahn  It is easy to make things.
It is hard to make things simple.