Hi Bastien,
please make sure to send your replies on the list, you'll get a
quicker answer.
Thanks for reminding, I keep forgetting.
As for requiring org-id for `org-open-at-point', I'm not sure this
is the right thing to do since it will require it for all users, even
those who don't use
Hi all,
I normally use the git master version of org-mode, so I didn't notice
this for the longest time, but my several of my updates to org-mode
still aren't merged into stable versions.
For instance, ob-J.el was added over a year ago, and there have been
stable releases since then, but it
Leo Ufimtsev lufim...@redhat.com writes:
Worf I think is a bit on the vi side of things. Helm is more generic.
Worf is as much on the vi side of things, as `org-use-speed-commands'
are. Almost not at all. It just takes vi-style hjkl arrows, because
Emacs-style bnpf arrows aren't convenient.
Leo Ufimtsev lufim...@redhat.com writes:
And it's got the best Helm implementation for navigating to
headings.
Well, when I hear someone use the word 'best', I see it as a challenge X-D.
I used worf-goto for a while. It's certainly amazing and on the odd occasion
I still use it, but lately
Hi Zhihao,
I’ve got a simple question: how to speed up jumping
between code blocks?
You might be interested in https://github.com/abo-abo/worf.
It allows you to traverse anything that starts with * or #+ with
just hjkl keys.
See the docs here: http://oremacs.com/worf/README.html.
regards,
Hi Rasmus,
On Thu, Apr 16, 2015 at 4:10 PM, Rasmus ras...@gmx.us wrote:
Hi Oleh,
Oleh Krehel ohwoeo...@gmail.com writes:
I was just trying to customize the completion back end for refiling (ido
isn't
great for that, even with the ido-vertical upgrade). And it's not at all
easy,
since
Hi all,
I was just trying to customize the completion back end for refiling (ido isn't
great for that, even with the ido-vertical upgrade). And it's not at all easy,
since ido seems to be hard-wired into org-mode's completion. Could we just
change to use `completing-read-function' instead of
On Thu, Apr 16, 2015 at 5:21 PM, Rasmus ras...@gmx.us wrote:
Hi Oleh,
Oleh Krehel ohwoeo...@gmail.com writes:
I was just trying to customize the completion back end for refiling
(ido isn't
great for that, even with the ido-vertical upgrade). And it's not
at all easy,
since ido seems
I don't know how to use helm of ivy. But I think the attached patch is
better. Would that work with helm and ivy?
Yes, both work fine.
I could live with it, but basically `org-completion-use-ido` says I
don't care if you've temporarily disabled `ido-mode' or not, I'll use
ido anyway. This
Hi Marcin,
On Thu, Apr 16, 2015 at 7:45 PM, Marcin Borkowski mb...@mbork.pl wrote:
On 2015-04-16, at 17:35, Oleh Krehel ohwoeo...@gmail.com wrote:
I don't know how to use helm of ivy. But I think the attached patch is
better. Would that work with helm and ivy?
Yes, both work fine.
Just
Hi all,
I don't know if this has been raised before, but it seems not to be
fixed yet. Currently, in HTML export, instead of #custom_id I'm getting
e.g. #orgheadline10.
The commit that broke this was 2 months ago:
160820bc9498e9364103e72b55a27cf92576dbb8 still works fine.
Let me know if this
Hi Nicolas,
Thanks for helping.
Nicolas Goaziou m...@nicolasgoaziou.fr writes:
The following buffer
* Headline
:PROPERTIES:
:CUSTOM_ID: my-id
:END:
exports as
div id=outline-container-orgheadline1 class=outline-2
h2 id=my-ida id=orgheadline1/aspan
Nicolas Goaziou m...@nicolasgoaziou.fr writes:
Oleh Krehel ohwoeo...@gmail.com writes:
It's not: I'm getting this in my Firefox address bar if I click the link:
testorg.html#orgheadline1
What link? There is no link in your example.
The link to the headline in the table of contents
Hi all,
The current `org-icompleting-read' is defined as taking only `rest
args', which can be as many as 8, all of them without a name.
I propose to update the definition to:
(cl-defun org-icompleting-read (prompt collection
key predicate require-match
Nicolas Goaziou m...@nicolasgoaziou.fr writes:
Moreover,
`org-icompleting-read' is not harder to read as `completing-read'
anyway.
I disagree on this. `completing-read' at least declares its own argument
list. So it's possible to distinguish which argument is which, albeit
with some effort
Hi Julien,
I asked this before, and the reason is that it was missed in the last
release. And there's still some time until the next release that will
finally update it.
regards,
Oleh
Erik Hetzner e...@e6h.org writes:
I believe that you can rewrite using the recoll tool directly instead
of recollq, using `recoll -t -b 'search string'`:
(defun counsel-recoll-function (string optional _pred rest _unused)
Grep in the current directory for STRING.
(if ( (length string)
Marcin Borkowski mb...@mbork.pl writes:
As Oleh Krehel pointed out in a reply to another mail of yours, if your
code links to org-mode code (or other GPL code) you cannot release it
under a different license. I'm not sure about how linking is intended in
Elisp sense of ('require)ing a library
Eric S Fraga e.fr...@ucl.ac.uk writes:
On Monday, 27 Jul 2015 at 19:04, Marcin Borkowski wrote:
[...]
Nope. As stated by someone here (Oleh, I guess), if I (require 'org),
or possibly even just write Elisp, and want to distribute it, it has to
be GPL.
I do not think this is true. I
Andreas Hilboll li...@hilboll.de writes:
Look here:
https://en.wikipedia.org/w/index.php?title=GNU_General_Public_Licensesection=11#Libraries
Most useful quote:
The Free Software Foundation (which holds the copyright of several
notable GPL-licensed software products and of the license text
Andreas Hilboll li...@hilboll.de writes:
However, when the interpreter is extended to provide “bindings” to
other facilities (often, but not necessarily, libraries), the
interpreted program is effectively linked to the facilities it uses
through these bindings. So if these facilities are
Eric S Fraga e.fr...@ucl.ac.uk writes:
Anyway, I think we've beaten this to death already. Time to get real
work done! :-)
That is my usual approach: label everything I write with GPL and not
think about it:)
It's just that most posts about GPL cast it in a bad light: I think it's
the best
Hi all,
I'd like to remove them in favor of using `org-icompleting-read'
everywhere (or better yet, `completing-read').
`org-completing-read-no-i' doesn't do much, is called twice and can be
replaced with a let binding wrapper.
`org-completing-read' could be updated this way:
(defmacro
Hi Xebar,
Xebar Saram zelt...@gmail.com writes:
i start using counsel and the counsel-recoll and is quite good, thx for this!
a small Q. when i launch the command am i supposed to see the search term
inline (like in grep) or just the file name it
resides in. currently i just see the
Hi Aaron,
Aaron Ecay aarone...@gmail.com writes:
Besides, CC-BY-NC-SA is compatible with GPL! Compatible. With GPL.
This isn’t correct. -NC licenses are non-Free (in the FSF sense of the
word): https://www.gnu.org/licenses/license-list.en.html#CC-BY-NC
-SA licenses are Free, but not
Hi Charles,
Charles Philip Chan cpc...@bell.net writes:
Just want to let you know, this commit:
,
| commit ceae5d651b80295f35c01ecfc53661c7e8eceba7
| Author: Oleh Krehel ohwoeo...@gmail.com
| Date: Tue Jul 28 15:06:25 2015 +0200
|
| lisp/org.el (org-set-tags): Simplify
Rasmus ras...@gmx.us writes:
Oleh Krehel ohwoeo...@gmail.com writes:
If anywhere in your code there's (require 'org), you have to release
your code under GPL.
Are you sure about that? By this logic, *any* .el file should be GPL as
they use (defun ·), implicitly loaded from byte-run.
I'm
Marcin Borkowski mb...@mbork.pl writes:
I'm preparing a tutorial on writing Org-mode exporters. To this end,
I'm writing a (simplistic) Oddmuse/WikiCreole exporter. Rather
obviously, I'm modeling it on existing exporters (mainly ox-latex),
which seem to share a lot of structure (function
Marcin Borkowski mb...@mbork.pl writes:
Hi all,
after a short discussion in a recent thread, I have a serious technical
question.
Assume that (for some reason) I want to write an Org-mode exporter which
won't be GPL'd. (Use-case: having written a few custom exporters, I'm
writing a
Hi Erik,
Erik Hetzner e...@e6h.org writes:
I previously hooked up org with recoll with pretty good results.
...
http://www.lesbonscomptes.com/recoll/
Thanks for the link. I tried it, and it actually works great on my
system (unlike swish-e). And I did no configuration of mimeinfo, I only
Marcin Borkowski mb...@mbork.pl writes:
And what if I explicitly want people to be able to use my code in
a proprietary software?
Then you're out of luck. Just like thousands (millions) of programmers
are out of luck when they want to examine the code of a closed source
proprietary software.
Aaron Ecay writes:
> Extra elisp inside the org file is an important way of extending the
> power of org markup. Why don’t you want to use it?
Including boilerplate Elisp, all subtly different into each markup
document, just to extend the markup with the syntax that it
Nicolas Goaziou <m...@nicolasgoaziou.fr> writes:
> Oleh Krehel <ohwoeo...@gmail.com> writes:
>
>> Is that a new feature?
>
> It is probably almost as old as Babel itself.
>
>> First time I've heard about it, and I did google
>> for inline code block ev
Hi Nicolas,
Nicolas Goaziou writes:
> There is already inline syntax for any language, including elisp:
>
> src_emacs-lisp{(foo)}
>
> and, if you use the library of Babel,
>
> call_foo{}
>
> I don't see the need to add yet another way to call inline code from an
>
Aaron Ecay writes:
Hi Aaron,
Thanks for the effort, I might use the code you suggested as a last
resort:)
I think the issue here is extending the power of Org markup.
The task at hand is "Write a manual in Org that exports to both Texinfo
and HTML", preferably with zero
Hi all,
I'm writing a manual in Org-mode, with the intent to export both to
Texinfo and HTML. And I'd like to use this link for Texinfo:
info:emacs#Packages
and this link for HTML:
https://www.gnu.org/software/emacs/manual/html_node/emacs/Packages.html
They both link to the same
Marcin Borkowski writes:
> Hi all,
>
> as in the subject. So, when I have e.g. [[foo][bar]], C-s finds bar,
> but not foo.
>
> Any way to find foo without e.g. temporarily resorting to text-mode?
The `swiper' command can do this. Available in GNU ELPA. I haven't used
`isearch'
Kyle Meyer <k...@kyleam.com> writes:
> Hello,
>
> Oleh Krehel <ohwoeo...@gmail.com> writes:
>
>> Hi all,
>>
>> Was the issue of abundant "Merge branch 'maint'" commit messages
>> discussed before? I couldn't find a reference...
>>
Hi all,
Was the issue of abundant "Merge branch 'maint'" commit messages
discussed before? I couldn't find a reference...
It's not a big deal, really, but I personally prefer to have linear
history with commits that actually do stuff. And it should be easy to
switch to this style: just use the
Kyle Meyer writes:
>> As far as I understood, maint is a subset of master, i.e. all commits
>> that are in maint are in master as well. Is that correct?
>
> Yes. As long as there aren't any new commits on maint that have yet to
> be merged
What is the purpose of maint exactly?
Stefan Nobis <stefan...@snobis.de> writes:
> Oleh Krehel <ohwoeo...@gmail.com> writes:
>
>> Would it be so hard for Git to perform a single merge of master into
>> maint on release, while keeping them separate and cherry-picking
>> in-between fo
Josiah Schwab writes:
Hi Josiah,
>> As I understood, for Org mode some commits are applied to maint, and
>> then merged into master. Why?
>
> It may be helpful for you to do a some background reading on workflows
> with git. Have you ever read the gitworkflows man page?
>
>
Achim Gratz <strom...@nexgo.de> writes:
> Am 11.09.2015 um 13:59 schrieb Oleh Krehel:
>> What is the purpose of maint exactly?
>
> It's a bit short on the explanation side, but does that help?
>
> http://orgmode.org/worg/dev/index.html
It does help a bit.
> Also
Hello,
I'm exporting an Org-mode document to Texinfo currently, but I'm having
an inconvenience with production of @subsubheading items.
What I'm doing right now:
#+BEGIN_TEXINFO
@subsubheading
#+END_TEXINFO
What I would like to have instead:
* :@subsubheading
Marcin Borkowski writes:
> Why?
Macro-expand the defun to get:
(defalias 'print-answer
#'(lambda nil
(message
"The answer is %s."
(forty-two
`lambda' is a macro that /quotes/ its body. Therefore, the body of
`defun' is not
At the current git master, the org source:
#+BEGIN_TEXINFO
@quotation
Permission is granted to copy, distribute and/or modify this document
under the terms of the GNU Free Documentation License, Version 1.3 or
any later version published by the Free Software Foundation; with
Kaushal Modi writes:
> The syntax change was announced in Dec last year:
> https://lists.gnu.org/archive/html/emacs-orgmode/2015-12/msg00525.html
>
> It is now
>
> #+BEGIN_EXPORT backend
> #+END_EXPORT
Thanks, Kaushal. I wasn't aware of the change.
I assume that
Samuel Wales writes:
> org-protocol works less than half the time now.
>
> i try it with the org-capture firefox extension on iceweasel. i also
> try it with a manual bookmark created by some instruction somewhere.
>
> today every click puts this in my messages buffer:
>
>
Nicolas Goaziou writes:
> So is Lisp.
I like Lisp.
> It boils down to ask users to write Lisp by hand at some point. Not
> everyone wants to use interactive tools.
I claim that a user can get by without having to write a single line of
Lisp manually. M-x `customize'
Nicolas Goaziou writes:
> Some users complained, and told me that "Org is not a programming
> language". Fair enough. Org has, indeed, to strike a balance between
> structure, required for efficiency and maintainability, and sloppiness,
> needed when you want to quickly
Nicolas Goaziou writes:
> I do not feel like asking users to write directly the AST for their
> plain text documents, really.
It's not an AST though. It's simply nested lists. Like JSON or XML but
better. And the idea is to both have it automatic and manual. For
example,
Hi all,
I've recently gotten back to reorganizing my Org setup. There are a few
things I find lacking, one of which is having all the auxiliary
information for a heading stored in a single place, that I can further
make less noticeable with `prettify-symbols-mode'.
(add-to-list
Nicolas Goaziou writes:
>> Here's a list of the diverse things that I'd like to hide into
>> :PROPERTIES:
>>
>> - Tags - there are always a pain to re-align, they show up as diffs in
>> git commits
>> - The clock entries - they are stored in a :LOGBOOK:, separately from
Nicolas Goaziou writes:
> Because not everything is a node property.
This shouldn't prevent us from keeping things that /are/ node properties
all in one place.
> TODO keywords, tags and properties are all different, and blurring the
> distinction between them would not
Kaushal Modi writes:
> Hi all,
>
> I have never published a package. I generally write elisp snippets embedded
> in my config.
>
> Here are my first attempts at a 'package' and defining a custom org
> export backend.
Congrats on your first package! It will surely come
Hi all,
I updated Org recently and noticed that the agenda display looks very
broken, especially in `org-agenda-log-mode'.
I did a bisect; reverting commit
912a385518bcf2e320cc161d573ad329111de6c7 fixes it.
Anyone else have this problem?
regards,
Oleh
Same happened to me.
Downgraded Firefox on Ubuntu 16:
apt-cache show firefox | grep Version
sudo apt install firefox=45.0.2+build1-0ubuntu1
sudo apt-mark hold firefox
Next, about:config / xpinstall.signatures.required:=false.
Finally, install 0.3.0.xpi from the website.
There's an
> Copying Oleh, as I believe he would also have some interest in this.
Thanks for the info. I still prefer to denote keys as ~C-x C-f~, and
code as =forward-char=:
1. It looks good in text.
2. It looks good on Github/Gitlab render.
3. It still exports as C-x C-f for HTML, and @kbd{C-x C-f}
for
Here's what I use:
(defun ora-ediff-prepare-buffer ()
(when (memq major-mode '(org-mode emacs-lisp-mode))
(outline-show-all)))
(add-hook 'ediff-prepare-buffer-hook 'ora-ediff-prepare-buffer)
regards,
Oleh
Hi all,
>> Would they need to install LaTeX too, or is org mode self-contained and
>> able to export to pdf without LaTeX an friends installed?
>
>
> Yes, they'd need to have a LaTeX distribution installed on their system. In
> my experience, installing the full latest version of TexLive is the
Hi Milan,
> Are there any tricks to speed it up?
I noticed org-drill being slow three years ago when I tried to learn it.
So I wrote my own package: https://github.com/abo-abo/pamparam/.
It's quite fast: it takes 0.6s to sync my 3300 cards from the master Org file.
And day-to-day learning
61 matches
Mail list logo