Re: [O] keybindings again...

[Kaushal Modi]

On Fri, Jun 30, 2017 at 1:12 AM Jean-Christophe Helary <
jean.christophe.hel...@gmail.com> wrote:

>
> Do you mean that Shift is not recognized as a modified key by the terminal
> ?
>

That's my understanding. Also, I rarely use emacs with -nw (as I would
otherwise miss PNG and PDF support), so I am not an expert on this subject.
But based on some reading, it has to do with the type of terminal emulator
you are using. This[1] might help.


> > If you do C-h c Esc+Shift+Return, Emacs will detect only Esc+Return. So
> you will see M-RET in the echo area.
> >
> > You probably just need to use some other binding.
>
> It would be nice if the org manual mentioned that too, and give
> alternative keybindings for use in the terminal because that's extremely
> confusing.
>

I cannot comment on that as this probably has to do with the terminal
emulator and not emacs. In any case, it might be better to submit an emacs
bug report (M-x report-emacs-bug) requesting this mention in the manual.

This node already mentions something on this topic:

(elisp) Other Char Bits

but just not using the "Ctrl + Shift + .." example.


[1]: https://emacs.stackexchange.com/a/13957/115
-- 

Kaushal Modi

Re: [O] keybindings again...

[Nicolas Goaziou]

Hello,

Jean-Christophe Helary  writes:

> It would be nice if the org manual mentioned that too, and give
> alternative keybindings for use in the terminal because that's
> extremely confusing.

It does: (info "(org) TTY keys").

See also `org-replace-disputed-keys'.

Regards,

-- 
Nicolas Goaziou

Re: [O] keybindings again...

[Jean-Christophe Helary]

> On Jun 30, 2017, at 11:51, Kaushal Modi  wrote:
> 
> On Thu, Jun 29, 2017 at 10:43 PM Jean-Christophe Helary 
> > 
> wrote:
> I'm using emacs built from master, emacs -nw, after moving .emacs.el and 
> .emacs.d away, on OSX 10.12.
> 
> 
> I'm trying to assign M-S-RET to org-insert-todo-heading because for some 
> reason it is not assigned by default: every time I hit ESC S-RET I get ESC 
> RET only.
> 
> It's the limitation of the terminal.

Do you mean that Shift is not recognized as a modified key by the terminal ?

> If you do C-h c Esc+Shift+Return, Emacs will detect only Esc+Return. So you 
> will see M-RET in the echo area.
> 
> You probably just need to use some other binding.

It would be nice if the org manual mentioned that too, and give alternative 
keybindings for use in the terminal because that's extremely confusing.

Jean-Christophe Helary 

Re: [O] org-protocol documentation

[Mario Martelli]

>> +worked for me on Windows-XP Professional and the emasc23 from 
>> ourcomments.org 
>> +(@uref{http://ourcomments.org/cgi-bin/emacsw32-dl-latest.pl 
>> }). I'm no Windows user
>> +though and enhancements are more than welcome on the org-mode mailinglist. 
>> The
>> +original file is from
>> @uref{http://kb.mozillazine.org/Register_protocol 
>> }.
> 
> Could someone double-check this?
> 
>> +@example
>> +REGEDIT4
>> +
>> +[HKEY_CLASSES_ROOT\org-protocol]
>> +@@="URL:Org Protocol"
>> +"URL Protocol"=""
>> +[HKEY_CLASSES_ROOT\org-protocol\shell]
>> +[HKEY_CLASSES_ROOT\org-protocol\shell\open]
>> +[HKEY_CLASSES_ROOT\org-protocol\shell\open\command]
>> +@@="\"C:\\Programme\\Emacs\\emacs\\bin\\emacsclientw.exe\" \"%1\""
>> +@end example
>> +
>> +@item
>> +macOS setup
> 
> See above.

As it seems Org protocol is not so popular :)

I assume there will be no feedback and it'll be sufficient to relegate to the 
OS documentation.

Especially the OS and 3rd party application related stuff made be anxious about 
rewriting the original documentation.

[O] Orgmode 9.09 and export of source blocks

[cedric simon]

Hi everyone,

I work with org mode for writing all my documentation and use source code
blocks extensively.
I don't know if I found a bug or something, but I encounter a strange
behavior with SQL source blocks.
Despite the settings I apply, they are always evaluated if I have ":exports
both" set.

I opened a discussion on reddit here:
https://www.reddit.com/r/emacs/comments/6k5t1h/orgmode_909_and_export_of_source_blocks/
if you want to see some input I already received.

This could be dangerous because in my documentation file, I have some
source blocks that delete records.
Since I don't have ":exports both" on them, they are not evaluated during
export.

I made a reproducible document, it's on gist, if you have time please have
a look:
https://gist.github.com/simonced/2a4ee29ed779a563b9fb7a9d8dcc83cf

Thank you for your time, any help will be appreciated.
Ask me any other details if you need, I'll do my best to answer quickly.


Cedric Simon

Re: [O] keybindings again...

[Kaushal Modi]

On Thu, Jun 29, 2017 at 10:43 PM Jean-Christophe Helary <
jean.christophe.hel...@gmail.com> wrote:

> I'm using emacs built from master, emacs -nw, after moving .emacs.el and
> .emacs.d away, on OSX 10.12.
>
>
> I'm trying to assign M-S-RET to org-insert-todo-heading because for some
> reason it is not assigned by default: every time I hit ESC S-RET I get ESC
> RET only.
>

It's the limitation of the terminal.

If you do C-h c Esc+Shift+Return, Emacs will detect only Esc+Return. So you
will see M-RET in the echo area.

You probably just need to use some other binding.
-- 

Kaushal Modi

[O] keybindings again...

[Jean-Christophe Helary]

I'm using emacs built from master, emacs -nw, after moving .emacs.el and 
.emacs.d away, on OSX 10.12.


I'm trying to assign M-S-RET to org-insert-todo-heading because for some reason 
it is not assigned by default: every time I hit ESC S-RET I get ESC RET only.

So, I tried things from
http://ergoemacs.org/emacs/keystroke_rep.html

First, this works fine:
(global-set-key (kbd "M-b") 'org-insert-todo-heading)

But this doesn't:
(global-set-key (kbd "M-") 'org-insert-todo-heading)

What I get here is the old M-return = org-insert-heading.

What is the problem here ?

Jean-Christophe 

Re: [O] Export results of code literal blocks (Jekyll directory structure) xpost emacs.stackexchange

[Jeremy Reeve]

On 29 June 2017 at 01:22, Nicolas Goaziou  wrote:
> Hello,
>
> Jeremy Reeve  writes:
>
>> Org-mode newbie here.  Please be gentle.
>
> Do you have any reason to think we will not be gentle?
>
>   "We have a squeaker today, class. Isn't he cute?"

That comment was totally inappropriate for a public mailing list.

>
> Can't you write a function that fixes generated links? See
> `org-export-before-parsing-hook'.

Yes I probably can.  I can think of many ways of doing exactly that.
I wasn't aware of the existence of the hook and that's why I chose to
ask. That's what I was looking for - a pointer. Thanks.

There seem to be many inconsistencies between the particular versions
I am using and the public documentation and I appreciate that the code
is probably evolving rapidly.  I note the difference in documentation
between master in the code repository and what is currently on the
public facing web site and that I ought to build the documentation
specific to the version I am using.  The experience gave me the
feeling that there might be something relevant which is not well or at
all documented.

If I read the entire reference manual of every piece of software I use
I would have no time to carry out the actual tasks I use these tools
for.  It would be morally correct to read the reference manual
cover-to-cover to find out the best approach to solving a problem.  I
think it is unfair to categorise this post as of the 'too lazy to look
up something in the manual' form as I had provided a concrete example
and what I wanted to achieve and as I tried to hint at - not a highly
experienced Emacs-lisp developer or emacs-org user having spent very
little time (a day) exposed to org-mode.  Occasionally one needs a
steer in the right direction, that is all.

I think what needs to be appreciated is that there will be a spectrum
of users on the one end who are active Emacs-lisp developers who have
familiarity with the codebase all the way to people appreciative of
the open source efforts but that do not have the time or inclination
to act as developers on yet another project unrelated to their work.

>
>> Also, the above snippet exports everything including the "BEGIN
>> export" which I think shouldn't happen but I'll examine that
>> separately.
>
> The closing line is wrong. It should be "#+end_export". Use `M-x
> org-lint' to find this kind of problem.

Yes. I found this immediately after posting and thanks for the tip
about org-lint.

Jeremy

Re: [O] bug?

[John Kitchin]

All I thought should happen is that the invisible text adjacent to the
point would be edited (except for the {}). Other than the edge case
where there is no first headline, it seems to work ok as far as I can
tell. 
  
Nicolas Goaziou writes:

> Hello,
>
> John Kitchin  writes:
>
>> I think there is a bug with invisible edits.
>>
>> In org 8.2.10 if I set this:
>>
>> (setq org-catch-invisible-edits 'smart) ; or show
>>
>> and have org-toggle-pretty-entities active, then if there is no headline
>> before point, with the point here:
>>
>> NH^{3}
>>   ^
>>
>> I get outline-back-to-heading: Before first heading if I try to type 
>> anything.
>>
>> I also get this same error in org 9.0.7. It only happens with the 3
>> wrapped in {}.
>>
>> That seems like a bug to me.
>
> Fixed, somewhat.
>
> I think `org-check-before-invisible-edit' deserves some discussion about
> its specifications. As-is, it contains logic errors. For example, if you
> try to edit text near invisible text and you happen to have invisible
> custom properties somewhere else in the buffer, the properties are going
> to be made visible but not the invisible text at point.
>
> I would be happy to fix this, but need to think about what is expected,
> e.g. when we are editing something near an invisible link or, as in your
> example, sub/superscript.
>
> Regards,


-- 
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] Org mode version 9.0.9 (9.0.9-elpaplus @ /home/jorge/.emacs.d/elpa/org-plus-contrib-20170622/); Org lost my state change note during idle clock resolution

[Jorge Morais Neto]

On 29 June 2017 at 17:11, Jorge Morais Neto  wrote:
> In two days this is the second time Org loses a TODO state change note
> draft.  I guess that, if I realize the note will take time to compose, I
> am supposed to compose it in some file and, only when it is ready,
> change state and yank it.
A correction: the previous draft loss was on Monday, not yesterday.
Still, I had two draft losses in four days.

Regards
-- 
- I am Brazilian.  I hope my English is correct and I welcome feedback
- 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/

[O] Org mode version 9.0.9 (9.0.9-elpaplus @ /home/jorge/.emacs.d/elpa/org-plus-contrib-20170622/); Org lost my state change note during idle clock resolution

[Jorge Morais Neto]

Remember to cover the basics, that is, what you expected to happen and
what in fact did happen.  You don't know how to make a good report?  See

 http://orgmode.org/manual/Feedback.html#Feedback

Your bug report will be posted to the Org mailing list.


I changed the TODO state and started composing a state change note.
Later I clocked in a certain task (automatically clocking out of the
previous) and left the computer.  When I returned, some 32 min later,
Org was showing clock idle time resolution.  I typed "i" to consider the
idle time as clock time.  The clock idle time resolution did its job,
but Org lost my note draft and the window configuration from before the
TODO state change.  winner-undo could not restore the window
configuration and AFAIK I had no way to recover the note.

In two days this is the second time Org loses a TODO state change note
draft.  I guess that, if I realize the note will take time to compose, I
am supposed to compose it in some file and, only when it is ready,
change state and yank it.

This time I do not have time to reproduce it in ~emacs -q~.  It happened
in the latest Spacemacs in holy mode.  Unfortunately
M-x org-submit-bug-report failed to collect my Org and Outline
configuration as I requested.

Regards

Emacs  : GNU Emacs 26.0.50 (build 1, x86_64-pc-linux-gnu, GTK+ Version 3.18.9)
 of 2017-06-07
Package: Org mode version 9.0.9 (9.0.9-elpaplus @
/home/jorge/.emacs.d/elpa/org-plus-contrib-20170622/)

current state:
==


-- 
- I am Brazilian.  I hope my English is correct and I welcome feedback
- 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] org-protocol documentation

[Mario Martelli]

Hi,

> Besides the changes suggested above, we should put some thinking in the
> structure, which may be not adapter for a manual.  In particular, it
> should be made shorter.

My attempt was to copy the existing documentation from worg to the core 
documentation and to leave as much as possible unchanged.

I also think that a much shorter documentation of Org protocol would be the 
better approach. 

> Also, index entries are sorely missing for now.


It seems that writing the documentation in Org and exporting it to texi might 
not be the best approach.

I’ll start with a fresh approach and try to bring up a short manual in org.texi.

BTW: Papers are signed

Kind regards
Mario
— 

Re: [O] bug?

[Nicolas Goaziou]

Hello,

John Kitchin  writes:

> I think there is a bug with invisible edits.
>
> In org 8.2.10 if I set this:
>
> (setq org-catch-invisible-edits 'smart) ; or show
>
> and have org-toggle-pretty-entities active, then if there is no headline
> before point, with the point here:
>
> NH^{3}
>   ^
>
> I get outline-back-to-heading: Before first heading if I try to type anything.
>
> I also get this same error in org 9.0.7. It only happens with the 3
> wrapped in {}.
>
> That seems like a bug to me.

Fixed, somewhat.

I think `org-check-before-invisible-edit' deserves some discussion about
its specifications. As-is, it contains logic errors. For example, if you
try to edit text near invisible text and you happen to have invisible
custom properties somewhere else in the buffer, the properties are going
to be made visible but not the invisible text at point.

I would be happy to fix this, but need to think about what is expected,
e.g. when we are editing something near an invisible link or, as in your
example, sub/superscript.

Regards,

-- 
Nicolas Goaziou

Re: [O] Org-capture templates target error in recent Org-mode source code update.

[Nicolas Goaziou]

Hello,

"numbch...@gmail.com"  writes:

> I'm using Org-mode source code "master" branch. and update to latest.
> (current latest commit: - 379a22c9c * master upstream/master Revert
> "ox-texinfo: Move menu handling from sections to headlines") My org-capture
> template works before, but now it does not work. Seems currently source
> code does not support "sexp" ~(file (car org-contacts-files))~ which
> returns a path to file.

See ORG-NEWS.

Regards,

-- 
Nicolas Goaziou

Re: [O] [bug?] org-inside-latex-fragment-p broken?

[Nicolas Goaziou]

Hello,

Rasmus  writes:

> First, we have to be careful because the cdlatex keys occupy a precious
> key.
>
> Second, it depends on the cdlatex function in question.
> cdlatex-math-symbol-alist already works outside of fragments and it
> probably should as it can be used to insert entities, such as "β".
>
> On the other hand, cdlatex-math-modify probably only makes sense inside
> fragments.  It is used to change characteristics of already inserted
> entity, e.g. make a character bold.  That typically only makes sense
> inside a math environment of some sort.

Well. Then, could your patch uses `org-backward-paragraph' instead of
plain `backward-paragraph'?

> Add to this, that something like "\mathbf{x}" isn’t "correctly"
> exported via ox, (it should then produce "$\mathbf{x}$").

Of course it is "correctly" exported. When you write raw LaTeX, Org
assumes you know what you are doing.

Regards,

-- 
Nicolas Goaziou

[O] Org-capture templates target error in recent Org-mode source code update.

[numbch...@gmail.com]

 I got this error:

#+BEGIN_EXAMPLE
Debugger entered--Lisp error: (error "Invalid file location: nil")
  signal(error ("Invalid file location: nil"))
  error("Invalid file location: %S" nil)
  org-capture-expand-file((concat org-directory "/Contacts/Contacts.org"))
  org-capture-target-buffer((concat org-directory "/Contacts/Contacts.org"))
  org-capture-set-target-location()
  org-capture(nil)
  funcall-interactively(org-capture nil)
  call-interactively(org-capture nil nil)
  command-execute(org-capture)
#+END_EXAMPLE

I define org-capture template with this:

#+BEGIN_SRC emacs-lisp
(setq org-contacts-files '("~/Org/Contacts/Contacts.org"))

(setq org-capture-templates
  (append '(("C" "[C]ontact"
 entry (file (car org-contacts-files))
 "** %^{NAME}
:PROPERTIES:
:NICK: %^{Nick}
:AVATAR: %^{Avatar}
:END:"
 :empty-lines 1
 :jump-to-captured t
 )
)
  org-capture-templates))
#+END_SRC

I'm using Org-mode source code "master" branch. and update to latest.
(current latest commit: - 379a22c9c * master upstream/master Revert
"ox-texinfo: Move menu handling from sections to headlines") My org-capture
template works before, but now it does not work. Seems currently source
code does not support "sexp" ~(file (car org-contacts-files))~ which
returns a path to file.


[stardiviner] GPG key ID: 47C32433
IRC(freeenode): stardiviner Twitter:  @numbchild
Key fingerprint = 9BAA 92BC CDDD B9EF 3B36  CB99 B8C4 B8E5 47C3 2433
Blog: http://stardiviner.github.io/

Re: [O] [PATCH] org-protocol: fixes open-source and extends rewriting of URLs

[Nicolas Goaziou]

Hello,

Mario Martelli  writes:

>  Could you provide an ORG-NEWS entry about it?
>
> Sure.

Applied. Thank you.

Regards,

-- 
Nicolas Goaziou

Re: [O] org-protocol documentation

[Nicolas Goaziou]

Hello,

Mario Martelli  writes:

> Please note, that the documentation assumes that the patches regarding
> “open-source” are applied.

Thank you.

> +You can set up Org for handling protocol calls from outside
> +applications that are passed to Emacs through the
> +@file{emacsserver}.  For example, you can configure bookmarks in
> +your web browser to send a link to the current page to Org and create
> +a note from it using capture (@pxref{Capture}).  Or you could create a
> +bookmark that will tell Emacs to open the local source file of a
> +remote website you are looking at with the browser.

There should be a menu here. "ox-texinfo.el" should take care of it
automatically.

> +@node About org-protocolel
> +@section About org-protocol.el

This should be @subsection About ...

But I think this can be merged with the paragraph above and the whole
section "About ..." removed.

> +@samp{org-protocol.el} is based on code and ideas from 
> @uref{./org-annotation-helper.org, org-annotation-helper.el} and
> +@samp{org-browser-url.el}.

I think we can remove the above since the references are not
particularly clear.

> +"@samp{org-protocol:/sub-protocol:/}" triggers actions associated with 
> @samp{sub-protocol}
> +through the custom variable @samp{org-protocol-protocol-alist}.

> +It comes with four predefined handlers:
> +@table @asis
> +@item @samp{org-protocol-store-link}

@code{org-protocol-store-link}

> + triggered through the sub-protocol "@samp{store-link}". Stores an 
> Org-link and
> +pushes the URL to the @samp{kill-ring}.

I think @samp{store-link} is sufficient, i.e., the double quote are
supererogatory.

Also

  ... the URL to the kill ring.

since we do not refer explicitly here to the kill-ring variable but
rather to the Emacs concept.

Note that Org manual requires two spaces after each sentence. There are
multiple occurrences to fix below.

> +@item @samp{org-protocol-capture}
> + Fill a @samp{CAPTURE} buffer with information gathered somewhere else. 
> This
> +handler is triggered through the "@samp{capture}" sub-protocol and uses the
> +function @samp{org-capture}.

See above about the quotes.

Also,

  @code{org-capture}

@code{} is preferred over @samp{} for functions, variables, and
syntactical elements in an Org buffer.

> +@item @samp{org-protocol-remember}
> + Fills a remember buffer with information gathered somewhere else. This

Note that it was "Fill" instead of "Fills" in the previous item. I'd
rather have the former.

> +handler is triggered through the "@samp{remember}" sub-protocol and still
> +available for backward compatibility. This handler uses @samp{org-remember}. 
> Use
> +the current @samp{org-protocol-capture}.

See above.

> +@item @samp{org-protocol-open-source}
> + "@samp{open-source}". Maps URLs to local filenames. Use this to open 
> sources of
> +already published contents in emacs for editing.
> +@end table

emacs -> Emacs.

The first sentence needs to be expounded.

> +@samp{org-protocol} helps creating custom handlers 
> @uref{../org-tutorials/org-protocol-custom-handler.org, (tutorial)} and so 
> called

We can remove the @uref since it points to a relative path from the
website.

> +@samp{org-protocol-projects}.
> +
> +
> +@@As of Org mode 9.0 a new org-protocol key=value syntax is supported@@

This syntax was removed in Org 8.0. You can delete the whole line.


> +Org-protocol can now handle query-style parameters such as:

It should be Org protocol, like Org mode, not Org-protocol.

> +@example
> +org-protocol://store-link?url=http:%2F%2Flocalhost%2Findex.html=The%20title
> +org-protocol://capture?template=x=Hello=World=http:%2F%2Fexample.com
> +@end example
> +
> +Old-style links such as
> +@samp{org-protocol://store-link:/http:%2F%2Flocalhost%2Findex.html/The%20title}
> +continue to be supported.

I wonder if it is useful to document old-style links at all in the
manual. Maybe as a footnote (i.e., @footnote{Old-style links...}) but no
more.

> +If you have defined your own handler functions for
> +@code{org-protocol-protocol-alist}, change them to accept either a property
> +list (for new-style links) or a string (for old-style links).  Use

This is very personal, but I don't like parenthesis outside Maths and
Lisp. In a document, they just break the flow of reading, even though
they are meant for side comments. Perhaps the following is better:

  If you have defined your own handler functions for
  @code{org-protocol-protocol-alist}, change them to accept either
  a property list, for new-style links, or a string, for old-style ones.

But, again, should we document old-style links?

> +@code{org-protocol-parse-parameters} to convert old-style links into property
> +lists.

See above.

> +@@As of Org mode release 7.01 @samp{org-protocol-remember} is now by 
> @samp{org-protocol-capture}.@@

See above.

> +If not stated otherwise, you may simply replace each occurrence of
> +@emph{capture} with @emph{remember} 

[O] Using org-mode via vSSH on iPad

[Peter Davis]

I've been trying to find a way to use org-mode from my iPad (other than
MobileOrg, which seems really unwieldy), and the closest I've come is to
us the vSSH app to connect to my desktop Mac and run emacs there.
Unfortunately, I'm running into some limitations and I'm not aware of
the workarounds, if any. I'm hoping someone here might know.
The most obvious is that after editing my org document, I want to export
to an HTML buffer from which I could copy and paste to Blogger (in a
browser). My normal key sequence
C-c C-e C-b h H

doesn't work, as the C-b seems to be treated as an ordinary 'b'. I don't
get a window showing me the HTML export. Anyone familiar with this or
how to get around it?
Then, does anyone know a way to copy the contents of the vSSH app
display to the iPad clipboard so I can paste into another app? I don't
mind having to edit out some amount of cruft that goes with it, as long
as I can get the basic HTML.
Thanks very much!

-pd

P.S. - I've also tried using the Editorial app with md format, but I
 really miss org's ability to format tables and lists on the fly.
 Editorial doesn't seem to do that.
--
  Peter Davis
  www.techcurmudgeon.com

Re: [O] org mode moves to GNU emacs core

[Uwe Brauer]

>>> "Rasmus" == Rasmus   writes:

   > Uwe Brauer  writes:
   >> I am not sure whether I understand that discussion in emacs dev
   >> correctly. Will orgmode be moved into the GNU emacs try as it was done
   >> with gnus?

   > AFAIK, there are no such plans.  The *version* of Org shipped with Emacs
   > is being updated to v9, though.

Thanks for clarifying.


   > But perhaps I missed a thread that explicitly talks about moving the
   > development center of Org...

More likely that I did not catch up the thread and panicked :-D

Re: [O] minitocs not displaying in latex export

[Rasmus]

Sharon Kimble  writes:

> I'm having great difficulties in getting minitocs appearing in my chapters. 
> This is my preamble -

Not quite answering your question, but did you try to use titletoc?

 * Chapter
 #+TOC: headlines 1 local 

Note that the package has to be loaded before hyperref.  See also the
manual under "Table of contents".

Rasmus

-- 
Hvor meget poesi tror De kommer ud af et glas isvand?

Re: [O] org mode moves to GNU emacs core

[Rasmus]

Uwe Brauer  writes:

> I am not sure whether I understand that discussion in emacs dev
> correctly. Will orgmode be moved into the GNU emacs try as it was done
> with gnus?

AFAIK, there are no such plans.  The *version* of Org shipped with Emacs
is being updated to v9, though.

But perhaps I missed a thread that explicitly talks about moving the
development center of Org...

Rasmus 

-- 
Governments should be afraid of their people

Re: [O] [PATCH] org-protocol: fixes open-source and extends rewriting of URLs

[Mario Martelli]

Applied. Thank you.Thanks to you :)I fixed some whitespace issue and typo in the test.:blush:  Thanks again.Could you provide an ORG-NEWS entry about it?Sure.

0001-ORG_NEWS-org-protocol-s-date-style-URL-support-is-me.patch
Description: Binary data
Kind regardsMario

[O] org mode moves to GNU emacs core

[Uwe Brauer]

Hi

I am not sure whether I understand that discussion in emacs dev
correctly. Will orgmode be moved into the GNU emacs try as it was done
with gnus?

If so, how can I download and test for example the current master
branch.

I didn't mind that policy for gnus, since the development is rather
slow and install GNU emacs every 6 months, but org mode is different
beast.

Uwe Brauer 

[O] [rows?] (was: org table toggle narrowing and true column hiding)

[Uwe Brauer]

   > Hello,
   > Uwe Brauer  writes:


   > I toyed a bit further with the idea, and re-designed the whole thing.

I tested it quite a bit yesterday. There was only one problem concerning
pabbrev mode which scans the buffer periodically and this scanning did
widen the columns at some point. One can try this out by running
(pabbrev-scavenge-buffer) in an org buffer with columns being narrowed:
the columns will widen. But I am not sure whether this is a bug of your
implementation. I am happy with turning pabbrev mode off in org buffers
with large table where I need to narrow.


BTW what's about hiding rows? For very long tables (~100 and more rows)
hiding can be convenient. I do that by running hide-region (a third
package found in elpa). But maybe that feature could be included in org
mode as well?

Thanks

Uwe Brauer