Jambunathan K kjambunat...@gmail.com writes:
I offer to take over maintainership of Org.
-1
François
P.S. I love the Org project, and I strongly hope it stay lovable. The
human qualities of a maintainer, and the crowd surrounding him/her, are
very important to me. In the past, I left
Thorsten Jolitz tjol...@gmail.com writes:
François Pinard pin...@iro.umontreal.ca writes:
Keep happy!
A bit discouraging, I must admit.
Don't be! We need all the courage we can get!
Keep going with 'poporg' and make it part of emacs/org-mode - and look
at 'outorg' as a proof
Jambunathan K kjambunat...@gmail.com writes:
Bastien b...@altern.org writes:
[...] to keep a nice atmosphere on the list, [...] put enough energy
to maintain the whole beast.
the estimation is done by managers themselves.
I find Bastien to be a very good maintainer. I maintained a good
Hi, gang.
I've difficulty to get the new exporter into movement. After trying for
some time, I'm giving into this mailing list for help or advice.
First, C-c C-e yields Cannot open load file: org-export. I guess
that some old autoload is hiding somewhere, but I just do not find it.
Command
Thorsten Jolitz tjol...@gmail.com writes:
With 'outorg', you can stay in you favorite language's major-mode while
programming, but with a real Org-mode 'look-and-feel', and rapidly
switch to a temporary buffer in Org-mode for some comment editing.
Exiting the temporary buffer then stores the
François Pinard pin...@iro.umontreal.ca writes:
Bastien b...@altern.org writes:
org-bullets.el is in the contrib/ directory.
Let me try to describe the problem. [...]
Hmph! My description was not accurate, as I can now observe. Here is a
correction. Instead of:
The header gets opened
Thorsten Jolitz tjol...@gmail.com writes:
[about the nearly coincident publication of *outorg* and *poporg*]
What a bad luck ... ;(
Oh, I'm not much into authorship wars, you know, as long as the need
gets covered. Free time being a scarce resource (for me at least!), I
prefer when we can all
Hi, Org friends.
Here is my weekly report on colorg development. colorg is a tool for
real-time collaborative edition meant for Org files in the long run, and
located at https://github.com/pinard/colorg.
There is a client in Emacs Lisp and a server in Python. There were no
change at all on the
Bill White bi...@wolfram.com writes:
C-c C-F (`org-next-block')
C-c C-B (`org-previous-block')
And, echoing Sebastien, `F' and `B' as speed commands would be very
handy.
Bastien b...@altern.org writes:
Of course, I just push this change.
Done!
Hi, all.
Quickly seeing this exchange,
Sebastien Vauban
wxhgmqzgwmuf-genee64ty+gs+fvcfc7...@public.gmane.org writes:
;;** 15.3 (info (org)Speed keys)
OK, got it now. I tried =?= as per the documentation suggests, and
there is a great deal there indeed.
Well, you know that since 25 Sep 2012 22:31; I remember an exchange on that
Gregor Kappler g.kapp...@gmx.net writes:
Cudos for all the work that has been done on migrating to the new
exporter. I so welcome that exporting now is approaching a clean
design!
Let me join my voice to the chorus! Munch congratulations, and thanks!
There is an impressive amount of work in
Bastien b...@altern.org writes:
42 147 aeus...@gmail.com writes:
Is there a way to see how many nested headlines there are within a
higher-level headline (not necessarily top-level)?
This is a nice feature of VimOrganizer but no, there is no way to do
this with Org for now.
Hi!
I'm not
Sebastien Vauban
wxhgmqzgwmuf-genee64ty+gs+fvcfc7...@public.gmane.org writes:
IIUC, this should (almost) answer the OP's request, by displaying the outline
path in mode line:
Oh, I completely missed the meaning of the OP request. Sorry for my noise.
François
Hi to all Org friends!
Here is my weekly status message on colorg development. colorg is a
tool for real-time collaborative editing of Org files. Interesting
progress has been made this weekend, but no cake yet! Sigh... :-)
There is an Emacs module and a Python server. The Emacs client has
Hi, Org friends.
Would someone be kind enough to point me in the right direction, if
there is one already? My need is to have conditional code at
publication time, and being able to include or exclude regions of code
according to some symbol being active or defined, or not.
The use case is a
Sebastien Vauban
wxhgmqzgwmuf-genee64ty+gs+fvcfc7...@public.gmane.org writes:
Hi François,
Hi, Sebastien! :-)
Please tell if that's more or less the direction you want to take...
Direction already taken, and completed a few minutes ago! :-). But I'll
happily revert to something else it if
Sebastien Vauban
For curiosity, why aren't you considering tangling?
Quick half of a reply, I'll revise the rest of your message later.
That would be far too much of a change for the habits of the team, or at
least, this is how I perceive the equilibrium between developers.
Moreover, some of
Bastien b...@altern.org writes:
I can launch a colorg server and two Emacs sessions. [...] Then,
making edits to any Emacs go to the other. That's a start!
It looks like a *pretty* good one! Can't wait to have a screencast
showing this :)
Thanks, Bastien. I begin to starve for getting
Loyall, David david.loy...@nebraska.gov writes:
https://github.com/ether/etherpad-lite/blob/master/doc/easysync/easysync-full-description.tex
Thanks for the link!
Implementing easysync in elisp would be valuable, not just for org-mode, I
think.
Likely! Yet maybe later for colorg, I want a
Hi, my Org friends.
The colorg project is about real-time collaborative editing of Org
files. The project progresses a bit on each weekend only, but I
seemingly cannot find free hours elsewhere in the week! Here is the
status after three weeks.
The parts slowly begin to fit together. I can
Samuel Wales samolog...@gmail.com writes:
What if we could have bidirectional links, and actually use an agenda
file for some of the entries instead of keeping the entries in the
non-Org file?
I'm not sure I understand the use case you have in head. Maybe
executable links could be helpful to
Hi, Org people.
It is often suggested that literate Org programming means interspersing
program fragments within an Org file. For practical reasons, I rather
prefer adding Org documentation into my programs. So this helping tool
which pops out a temporary Org mode buffer with the contents of
Daimrod daim...@gmail.com writes:
François Pinard pin...@iro.umontreal.ca writes:
ColOrg is a project about real-time collaborative editing of Org files.
That's a really cool project!
Thanks.
Do you plan to keep the server in Python? Or do you think it would be
possible to make
Hi to all my Org friends.
ColOrg is a project about real-time collaborative editing of Org files.
Here are some news about its progress, after a second push this
weekend. It is not usable yet, but a few more steps have been taken. A
few more ropes are needed to tie it up all together, but not
Hi, Org people.
I just noticed that org-store-link has been improved, and now uses
#+TITLE contents by default when executed before the first header.
Thanks for this improvement which, even if tiny, is helpful to me!
The fun thing is that I found it by mistake. Because org-store-link did
not
[Oops, might have C-c C-c'ed in the wrong buffer! :-)]
Hi, Org people.
I just noticed that org-store-link has been improved, and now uses
#+TITLE contents by default when executed before the first header.
The fun thing is that I found it by mistake. Because org-store-link did
not save a
Samuel Loury konubi...@gmail.com writes:
But instead of creating your own protocol, have you thought about
extending an already existing one?
Yes, of course. My goal is getting some solution, not creating my own
thing. I only tried to look at the internals of Rudel and
Etherpad-lite, and
Hi, Org people.
This is for current Org (7.9.3d-827-g7cd81b, says the manual). In node
node Checkboxes, near the end, we read:
(3) `C-u C-c C-c' on the _first_ item of a list with no checkbox will
add checkboxes to the rest of the list.
It seems it only works for external checklists, but
Hi, Orgers!
Here are some development news about ColOrg, which is a tool meant for
real-time collaborative edition for Org files. I pushed a bit on the
project this weekend, but now, job duties might force me to delay
further work until next weekend.
I'm not done yet with the initial writing,
Torben Hoffmann torben.leh...@gmail.com writes:
Not sure if it would be speedy enough, but gitit [...]
Thanks for the pointer! :-)
Inventing a protocol to deal with synchronisation is not trivial, so a
good starting point might be gitit or raw git with the intention of
learning about what
François Pinard pin...@iro.umontreal.ca writes:
So, inventing a protocol is still an avenue which I naively seek, and
for which I dared giving some thought recently, trying to stay on the
side of simplicity.
Here is a stab at a simple protocol, which I documented in:
https://github.com
Hi, people.
A few weeks ago, we had a short discussion on this mailing list about
creating a Collaborative Org project. Well, I see that my need just
does not fade out. So this morning, for the good or for the bad,
without knowing where this will bring me :-), I decided to give in and
just
Hi, Org people.
Let me report an old problem of mine about missing fontification in Org
tables. In my .emacs file, I have:
(defun fp-fontify-fixme ()
(font-lock-add-keywords
nil '((\\FIXME\\ 0 font-lock-warning-face t
(let ((hooks '(c-mode-common-hook change-log-mode-hook
Bastien b...@altern.org writes:
(defun fp-fontify-fixme ()
(font-lock-add-keywords
nil '((\\FIXME\\ 0 font-lock-warning-face t)) t))
HTH,
IDHITAL = it did help indeed, thanks a lot! :-)
I had more fontification to do in some tables, and succeeded because of
your good hint. Joy! :-)
Jambunathan K kjambunat...@gmail.com writes:
2. Turn on Hi-lock mode
Wow, Jambunathan, thanks as well! I was not aware of this mode, which
announces to be useful and handsome, especially when some often visited
files would benefit from some very specific highlighting. How nice!
François
Eric Schulte schulte.e...@gmail.com writes:
Unfortunately Rudel doesn't appear to be maintained [...]
Moreover, looking around, I saw a few comparisons and comments in which
other tools using the Obby protocol, which Rudel primarily supports, had
negative light. I also found out that the
Bastien b...@altern.org writes:
Would you like something like
| 3.1 |
| 3.1415 |
be aligned/modified as
| 3.1000 |
| 3.1415 |
?
More precisely as:
| 3.1|
| 3.1415 |
which is aligning on dots, even if it looks like left-justifying.
There is a problem in that I have tables
Dov Grobgeld dov.grobg...@gmail.com writes:
Nice! I've needed that often. But please add licensing information
to the code to make clear in what contexts it may be used.
You mean, for the Python bits I sent to the list? For such a short
amount of code, do whatever you feel like it. If you
Bastien b...@altern.org writes:
I don't have experience with Rudel but I'm also interested in hearing
from others -- maybe at some point we can organize some co-writing
session where we try to update Worg pages.
I tried Rudel, a good while ago, and did not find it satisfying enough
to be
François Pinard pin...@iro.umontreal.ca writes:
Bastien b...@altern.org writes:
[...] let *anyone* write Org doc collaboratively and seemlessly.
Com'on, let's start something great :)
It would be great indeed!
On the road this morning, I gave some thought on this problem, which
does
Bastien b...@altern.org writes:
Hi François,
Salut, et Joyeuses Festivités! :-)
I recently needed to produce Org tables from within Python
Thanks for the code, if some can test it and put it on worg, all the
better (if you agree of course.)
Of course!
I wrongly thought Org mode was
Hi, Org people.
I recently needed to produce Org tables from within Python, splitting
them as needed to fit within a preset width. I append the code after my
signature, in case it would be useful to others (or even, if you have
ideas to improve it).
One thing I only realized after writing this,
t...@tsdye.com (Thomas S. Dye) writes:
My goal at this point is to export a document that matches org.texi.
So nice! :-)
I guess I would be much happy myself if I could use Org rather than
Texinfo for some of my own documents. Thanks to all involved! :-)
François
Michael Brand michael.ch.br...@gmail.com writes:
Hi François
Hello, Michael!
To check the invisible parts of an Org link here are some alternatives
to Fundamental mode that stay in Org mode:
1) M-x org-toggle-link-display
2) M-x visible-mode(also toggling)
3) temporarily delete the
Ian Barton li...@wilkesley.net writes:
Thanks Carsten,
Works perfectly.
On 22/10/12 13:59, Carsten Dominik wrote:
you need to use #+setupfile instead of #+include for this purpose.
On 22 okt. 2012, at 14:39, Ian Barton li...@wilkesley.net wrote:
I thought I would define them in another
James Harkins jamshar...@gmail.com writes:
But I'm running into the limitation that plain lists can't be sorted
*by their checklist status*. You can sort alphabetically, numerically
or by time or function.
Hi, Org people.
Just quickly perusing this list, this message reminds me of an old
Nicolas Goaziou n.goaz...@gmail.com writes:
Therefore, I don't see any reason to keep maintaining the #+SETUP_FILE
keyword. I'd rather remove it and suggest to use #+INCLUDE: keyword
instead. Any objection?
None really. I use both and distinguish them in some validation tool,
which I would
Hi, Org people.
I just refreshed Org mode from Git today, and as usual, it was fairly
easy. From the announcement, tons of work accumulated, and I wanted to
take advantage of them! It's fun putting oneself in a position to
lazily discover new possibilities over something which is already highly
t...@tsdye.com (Thomas S. Dye) writes:
Aloha François,
Hi, Thomas!
Have you discovered :colnames and :rownames? These two header arguments
might do what you want.
Yes indeed, they do! Easier and less cumbersome this way! Thanks a lot
for the hint.
Have a nice day!
François
Hi, people. A tiny detail while perusing around. In page:
http://orgmode.org/worg/org-contrib/babel/intro.html
with the section about R, for the second box showing /HTML export of
code/, the second line does not correspond its source in the first box.
François
Hi, Org people.
A while ago, I started to get acquainted a bit with Babel, mainly as a
curiosity for an area of Org I did not know nor use yet. However, for a
couple of weeks now, I'm starting to better understand how useful the
combination of Babel and R may be in real situations.
While
suvayu ali fatkasuvayu+li...@gmail.com writes:
For step by step instructions you can look in the following FAQ entries:
http://orgmode.org/worg/org-faq.html#Keeping-current
Without being fully sure, and while the above procedure long worked
without problem for me, I think that more recently, I
suvayu ali fatkasuvayu+li...@gmail.com writes:
On Mon, Jun 4, 2012 at 3:58 AM, François Pinard pin...@iro.umontreal.ca
wrote:
My feeling is that ideally, Org should itself provide a standard Org
exporter, as generic as it should be.
C-h f org-export-as-org [RET]
Wow! Thanks
Hi, Org people!
GitHub renders a README.md file right at the end of the project page,
using bigger fonts for titles, producing clickable links, and such
things. As I did not feel like maintaining the same information both in
Org and Markdown format, I used the Org - [org-publish] - HTML -
Hi, people.
On the nomenclature issue of our preferred tool, if I had my say, I
would suggest Org, and drop mode. Org is really a major Emacs mode,
in many acceptations of the word major. We should speak of Org the
same way we speak of Calc or Gnus (or Dired).
Of course, these all have a mode,
Nick Dokos nicholas.do...@hp.com writes:
François Pinard pin...@iro.umontreal.ca wrote:
Using C-c C-l to create a link, I'm replying to the two prompts with the
following contents: [...]
FWIW, I can't reproduce this problem. Here is how I tested:
[...]
Thanks a lot for having tried, Nick
Hi, people.
Using C-c C-l to create a link, I'm replying to the two prompts with the
following contents:
Link: http://www2.stm.info/taz/horaire.php?l=29d=Et=52103
Description: Autobus 29 est
The link is then saved as (using fundamental-mode to see it):
Hi, gang!
Just discovering org-crypt.el today. Wow! I can distribute all the
information in many Org files instead of keeping it all in a single
crypted file, that is, where each fragment really belongs. Moreover,
headings stay searchable! Congratulations and thanks to the authors.
François
Hi, Org people.
When I save a heading with C-C l, a later insertion using C-c C-l
recovers the heading as the default description. Which is nice!
When I position the cursor at the beginning of the Org buffer, before
any heading, usually on the #+TITLE line, before doing C-c l, there is
no
François Pinard pin...@iro.umontreal.ca writes:
Nicolas Goaziou n.goaz...@gmail.com writes:
I'd rather pull you into writing a Texinfo back-end for the export
engine ;)
Well, Nicolas has been much helpful at getting me started on this one.
I might aim Python.
Nicolas' works are so nicely
On 31.3.2012, at 21:24, Stephen J. Barr wrote:
I want to make a document that has a table where one column has
variables and another column has descriptions.
| VAR NAMES | DESC |
|---+|
| =var1=| this is the first var |
| =var2=|
Nick Dokos nicholas.do...@hp.com writes:
François Pinard pin...@iro.umontreal.ca wrote:
If I had to do this, I would search around to see if there is an Org to
Texinfo exporter, and then blindly / fully rely on it to do various
wonders automatically! ;-) I did not check, but presume
Hi, Org people!
A while ago, we discussed capitalization on this list, as the manual was
irregular on things like #+BEGIN_SRC and #+begin_src. After some
discussion and hesitation, Bastien decided to stick to upper case in the
manual, and despite it was not my own preference, I amended all my
Nick Dokos nicholas.do...@hp.com writes:
If the real source of the manual was in Org format, and periodically and
mechanically turned into a Texinfo file, would the requirement be met?
Yes, but somebody would have to write a good texinfo exporter.
Oh! I did not even know that none exist
Bastien b...@gnu.org writes:
Sebastien Vauban
wxhgmqzgwmuf-genee64ty+gs+fvcfc7...@public.gmane.org writes:
These last days, I've observed that, whenever creating a new Org file
(to be precise, when saving it), I'm asked:
non-existent agenda file ~/file.txt. [R]emove from list or
François Pinard pin...@iro.umontreal.ca writes:
I could of course modify my nit-picking program so it recognizes the
#+RESULTS: case, but my feeling is that Org should be consistent overall
on capitalization. And by telling this, of course, I disregard my own
preference. Consistency has
Nicolas Goaziou n.goaz...@gmail.com writes:
No, org-export needs testing, and I'm ready to debug it. [...] I do
not ask you to debug anything, but, if you can provide them, ECM help
a lot. In any case, please report the problems you get with it.
[...] I think reporting to this list is
Hi.
Page http://orgmode.org/worg/org-contrib/org-drill.html refers to
inexisting http://orgmode.org/worg/org-contrib/spanish.html. There is
no spanish.org in the Org mode distribution either. Maybe here?
https://bitbucket.org/eeeickythump/org-drill/src/bc740455003b/spanish.org
François
Hi, Org people.
GitHub has a few niceties, like easy forking, pull requests and such. I
notice https://github.com/jwiegley/org-mode in particular, which does
not seem to be itself a fork of another GitHub repository, so I presume
it forked directly from the official Git site for Org mode, which
Hello, Org people.
Seeing again the (org) Languages node in the manual, I decided to check
all my #+BEGIN_SRC for language tags, which I too often improvise, for
normalizing them. I noticed a few things, and wonder if the manual
should be amended, or if I should change my habits instead.
- I
t...@tsdye.com (Thomas S. Dye) writes:
Aloha François,
:-)
Do you know how to do this in texinfo?
If I had to do this, I would search around to see if there is an Org to
Texinfo exporter, and then blindly / fully rely on it to do various
wonders automatically! ;-) I did not check, but
Nicolas Goaziou n.goaz...@gmail.coma writes:
Richard Lawrence richard.lawre...@berkeley.edu writes:
I have seen mention of the new exporter on this list a bit [...] How
can I try it [...]?
Assuming contrib directory is in your load-path, just evaluate
(require 'org-export)
It would be
Christian Moe m...@christianmoe.com writes:
- You can simplify repeated use with macros. See the manual, section
11.6. Use the @ notation (section 12.5.3) for literal html tags within
the macros. E.g.:
#+MACRO: mycolor @span style=color: black; background-color:
#f4a460$1@/span
Christian Moe m...@christianmoe.com writes:
There are other drawbacks [to macros], such as needing to
backslash-escape any commas (as in the above example).
Oh, thanks!
This (partly) replies to the message I sent a few minutes ago. Before
sending that message, I checked in the Org manual,
Rainer M Krug r.m.k...@gmail.com writes:
I would like to use a README.org file on github, and also include code
blocks in the README.org - is this possible?
Hi, Rainer. I'm not sure I'm really replying to your request, but
nevertheless hope my comments might be useful.
Having recently had a
Nicolas Goaziou n.goaz...@gmail.com writes:
This is correct. I was just pointing out (though, admittedly, not very
clearly) that the final part of the next sentence in the manual,
sometimes it is convenient to put them into a comment line, isn't.
It might be worth making the manual clear, so
Hi, Org people.
I'm not sure I'm using # tag correctly, but my feeling is that it
should stick to the following text in various Org operations. Let's say
I have something like (as I think it):
--8---cut here---start-8---
* Some container
# tag1
* Title 1
Nicolas Goaziou n.goaz...@gmail.com writes:
# tag is a deprecated construct.
Sigh! I just spent a few hours adding many of those and making sure
everything is regular.
When some feature is being deprecated, the Org manual should tell us,
then ! :-) And at least where that feature is
François Pinard pin...@iro.umontreal.ca writes:
Nicolas Goaziou n.goaz...@gmail.com writes:
I suggest to avoid bothering with it.
I hope the letter I wrote at the beginning of this little thread is
not going to be dismissed or ignored.
Well, my original message accidentally left my machine
Bastien b...@gnu.org writes:
Hi François,
Bonjour chez vous! :-)
François Pinard pin...@iro.umontreal.ca writes:
There is some machinery on my side involved into publication, which I
would rather avoid if not necessary.
Please don't hesitate to share it you think other people could find
Bastien b...@gnu.org writes:
Does #+INCLUDE: suits your needs?
Oh! I never used a colon after #+INCLUDE. Checking the Org manual, the
colon is systematically there, except within the last paragraph of node
/Updating files/. Maybe it could be added for consistency?
I did not notice my error
François Pinard pin...@iro.umontreal.ca writes:
Our dear Bastien writes:
We could have a #+PUBLISH: option allowing to tell whether a file
should be published or not. If we had this, we could then check
whether a section without the :noexport: tag has been modified...
and dynamically set
Hi, people. I doubt there is an easy solution, but here I go nevertheless.
Many of my Org notes are published to the Web, which have :noexport:
headers. It is very convenient that Org allows me to keep all parts
together, whether parts are published or not, in a single Org file.
There is some
Bastien b...@gnu.org writes:
Hi François,
It now seems that UNDER\_LINE, while producing HTML, is now rendering
the backslash instead of removing it. [...] I would not be tempted
to think the upgrading of Ubuntu has a consequence on the Org changes
I'm seeing.
Can you give us a hint on
Hi, everybody.
I might not be following the mailing list closely enough… May I check
with you, just in case I should rather chase an error on my side?
* It now seems that UNDER\_LINE, while producing HTML, is now rendering
the backslash instead of removing it. The backslash was previously
William Gardella gardell...@gmail.com writes:
If you close the group with `gnus-summary-exit-no-update' (the Q key
in default binding), these messages will not be marked as read.
Indeed, thanks William!
Now, I just have to be careful enough to remember to use Q instead of
q! When flying
Hi, Org friends.
I'm just noticing that ID: properties are now being created whenever I save
a link. I presume this is a recent change.
The ID does not encode the file, so I'm tempted to presume that Org
ought to read the target Org files for discovering where are the IDs.
As Org is surely not
Hello.
In my Org files, I have many references to Gnus articles which are part
of mailgroups. When batch reading email with Gnus, I'm OK with the
newsreader paradigm, in which an article is almost deleted as soon as it
gets read: it will not show the next time I'll visit the group.
However,
Hi, Org people.
I decided to clean up all those emails lying around in my notes, and
better validate ~/.ecompleterc against other Org information I have. A
bit of a burden to do, but I guess it has to be done one day.
There are many occurrences of u...@domain.name notations in my
files, which I
pin...@iro.umontreal.ca (François Pinard) writes:
Is there some easy way to get Org to read and understand the older
u...@domain.name notation as meaning the same as the equivalent
mailto:u...@domain.name; notation, and then, of course, behaving like
it? Or else, should I rather just forget
Hi, Org people!
Now that many Org files are part of my agenda list, it became more
likely that I inadvertently kill one of them. Then, commands like t
or RET in the agenda fail.
--8---cut here---start-8---
Debugger entered--Lisp error: (wrong-type-argument
Nick Dokos nicholas.do...@hp.com writes:
François Pinard pin...@iro.umontreal.ca wrote:
Now that many Org files are part of my agenda list, it became more
likely that I inadvertently kill one of them. Then, commands like
t or RET in the agenda fail. I have to first revisit the Org
file
Bastien b...@gnu.org writes:
Hi François,
Bonjour, Bastien!
I added Du as a prefix to get going, but the ideal would be to
directly use 2012-02-29 as the link description. Is there a way, or is
it a limitation (or a bug)?
I would call it a limitation.
Could it be documented somewhere
Nicolas Goaziou n.goaz...@gmail.com writes:
Just use two different drawer names, and select which one to actually
export through i.e. #+OPTIONS: d:(EN). No need for extra syntax.
Well, the manual says, in node Export options:
d: turn on/off inclusion of drawers
So one would
Memnon Anon gegendosenflei...@googlemail.com writes:
pin...@iro.umontreal.ca (François Pinard) writes:
I often cut a list item (or a hierarchy of list items) to reinsert it
into another heading which I know contains only list items. All the
headings are collapsed, so what I usually do
pin...@iro.umontreal.ca (François Pinard) writes:
[...] so what I usually do is position the cursor at
the beginning of the /next/ heading and yank the list item there. [...]
However, by mistake, it happens that the cursor is on the only visible
bullet star of the next heading (I'm using
Hi everybody.
Here I am with yet another need for an Org solution. There should not
be much remaining! I'm sure they *all* say that... :-)
I have a set of Org files with links to one another, for which I publish
a dozen Web sites or so (using org-publish-project-alist). Whenever a
link is
Hi, Orgers of this world! :-)
I do not find how to mix COMMENT and TODO in a working way, and I
thought that someone could advise me.
For ease and simplicity, I try to keep everything related to some topic
in a single file, merely commenting (C-c ;) headers for those parts I do
not want to
Bastien b...@gnu.org writes:
then I get the display I wanted. Is there a way for having #+ATTR_HTML
to be applied to the inner tag instead of the outer one?
Not -- it would not make sense.
Hello, Bastien.
I understand what you mean by saying it does not make sense with the
current
suvayu ali fatkasuvayu+li...@gmail.com writes:
François Pinard pin...@iro.umontreal.ca wrote:
I would also like to keep my TODO entries for this topic in the same
file, and these are usually not to be published either.
Just use the noexport tag on the parent tree with the TODOs.
* Tasks
101 - 200 of 323 matches
Mail list logo
