[O] Filter depending on item level
Hi guys, Is there a way to filter the agenda based on the level of the item. For example, let's say I have several items tagged as projects, but I would like to get a list of projects that are 1st or 2nd-level items in my org files, like: * This would appear :project: * This would also :project: * This would not appear :project: Is there an easy way to do this currently? Thanks, - Marcelo.
Re: [O] local.mk and SUDO
Martyn Jago writes: > So the obvious answer is to not to use make install (as per the > documentation). This is a heads-up to me since I believed install did > more than simply moving .el and .elc files from A to B. You can use "make install", but you must never install into the source directory. I'll check if changing the install mode to 644 is OK. > However this is new behavior and worth mentioning. 'make install' (no > sudo) used to silently `install' (or not as the case may be) and not > change modes as above. Personally I wouldn't call it a regression though > since make install is pointless IIUC in this situation. If install were to use "cp", then you might even lose data when you try to install into the same directory. Don't do this, prefix must not point to the git directory! > Since I can no longer use `make up2' it seems that `make up1' is the > correct command for my situation. This works fine except that > org-version points to the wrong org-install: > > Org-mode version 7.8.09 > (release_7.8.09-441-g6732d6.dirty @ > /Applications/Emacs.app/Contents/Resources/lisp/org/org-install.el.gz) > > So for my case I've added the target upgrade to local.mk: > > upgrade: up1 autoloads Correct. Regards, Achim. -- +<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+ Samples for the Waldorf Blofeld: http://Synth.Stromeko.net/Downloads.html#BlofeldSamplesExtra
Re: [O] missing autoloads / (void-variable org-version)
Michael Sperber writes: > Yes. I've also had to apply a few fixes to make the current XEmacs > work. I intend to send a new batch of patches in two weeks or so, once > everything has settled down on my end. (Until then, I'm quite swamped. > If I don't answer e-mail in that timeframe, please don't assume I'm not > interested.) I have found a few things to adapt, it does at least compile (even if XEmacs complains a lot). Testing is unfortunately not possible, unless somebody has ert ported to XEmacs (prominently, XEmacs doesn't have button.el). Regards, Achim. -- +<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+ SD adaptation for Waldorf rackAttack V1.04R1: http://Synth.Stromeko.net/Downloads.html#WaldorfSDada
Re: [O] mail integration, advice?
On søn 29 apr 2012 02:45:54 CEST, Neil Smithline wrote: > On 4/27 08:09 , Stephen Eglen wrote: > > A relatively new emacs mailer, mu4e, is worth mentioning: > > > > http://www.djcbsoftware.nl/code/mu/mu4e.html > > > > I really like it so far + it has support for org mode links. > > Stephen, > > I didn't know about mu4e. I've played around with mu in the past and > thought it was very cool but couldn't really work it into my daily > workflow. mu4e seems to handle that. > > Are the directions at > http://www.djcbsoftware.nl/code/mu/mu4e/Gmail-configuration.html really > all it takes to get this running? If so, I'm definitely going to give it > a whirl. > > Neil Smithline > http://www.neilsmithline.com > Proud GNU Emacs user since 1986, v. 18.24. > > I have been through WL, gnus, mutt and I haven't really been satisfied with any of them. But then I tried mu4e, and I really like it. What I particularly like is the search function, the interface as well as the org-mode integration, and it's pretty easy to set up! Mikkel Kristiansen
Re: [O] full path to result image?
I figured it out. Was not working because of my mistakes in header. But now I get another problem. Images are not converted during export to pdf or odt. And if I enable inline images only small empty square appears. What could be wrong with my setup Thanks __ Petro
[O] full path to result image?
Hi all.
I try to incorporate a python generated image as result of python
block execution.
how can I use full path to the image
something like:
#+BEGIN_SRC python results: /home/petro/mydoc/estimated_spectra_cl.png
.
plt.figure()
plt.plot(spectra[:,0],spectra[:,1:])
plt.grid(1)
# plt.show()
plt.savefig("/home/petro/mydoc/estimated_spectra_cl.png",dpi=100)
#+END_SRC
--
__
Petro Khoroshyy
Re: [O] Documentation vs. implementation for org-properties-postprocess-alist
Hi Bill, all right, I pushed this minor change. Thanks, -- Bastien
Re: [O] Documentation vs. implementation for org-properties-postprocess-alist
Hi Bastien, I just did a pull this morning against the latest in git and the code is the same. The definition of the variable org-property-postprocess-alist says that it should be a list of lists where each inner list's car is a string and cdr is a function. I think the doc string for the variable sounds right. But if you look at the function org-set-property what it does is set fn to (assoc property org-property-postprocses-alist), which is a list whose car is property and cdr is the function. Then later the function does (funcall (cadr fn) value). The cdr of fn is the (lambda () ...) function. I'm not sure what the car of a lambda function is, but it's not what should be passed to funcall. Instead what I think should happen is that fn should be set to the lambda function itself initially by calling cdr on the result of assoc. Now fn has the lambda function as it's value, so that later on when the test for non-nil fn is done you can then simply do (funcall fn value) without the extra cadr. Another fix would be to change the cadr of fn to just cdr of fn. But then the test says if the list is non-nil then call the function which is the cdr of fn, but that could be nil at that point since it wasn't checked. Best, ~>Bill On Sun, Apr 29, 2012 at 2:43 AM, Bastien wrote: > Hi Bill, > > Bill Wishon writes: > > > While hacking around I read the doc for > > org-properties-postprocess-alist and I think it doesn't align with > > what the implementation of org-set-property does. > > I don't see anything wrong. Can you double-check? If there is a > problem, please tell us what version of Org you are using. > > Thanks, > > -- > Bastien >
Re: [O] local.mk and SUDO
Achim Gratz writes: > Martyn Jago writes: diff --git a/lisp/org-mobile.el b/lisp/org-mobile.el old mode 100644 new mode 100755 [...] > Then you yourself must most likely have changed the mode of those files > to "executable". There is nothing in the build system that even > attempts to change modes. Hi Achim Since the new makefile uses the `install' command as opposed to `cp' to install files, the following is noted in man install: ,[*Man install*] | -m Specify an alternate mode. The default mode is set to rwxr-xr-x | (0755). The specified mode may be either an octal or symbolic value; | see chmod(1) for a description of possible mode values. ` Since the mode of .el files on git is 0644, this causes git to flag the files as modified (since I am running Org from the distribution directory). So the obvious answer is to not to use make install (as per the documentation). This is a heads-up to me since I believed install did more than simply moving .el and .elc files from A to B. However this is new behavior and worth mentioning. 'make install' (no sudo) used to silently `install' (or not as the case may be) and not change modes as above. Personally I wouldn't call it a regression though since make install is pointless IIUC in this situation. Since I can no longer use `make up2' it seems that `make up1' is the correct command for my situation. This works fine except that org-version points to the wrong org-install: --8<---cut here---start->8--- Org-mode version 7.8.09 (release_7.8.09-441-g6732d6.dirty @ /Applications/Emacs.app/Contents/Resources/lisp/org/org-install.el.gz) --8<---cut here---end--->8--- So for my case I've added the target upgrade to local.mk: --8<---cut here---start->8--- upgrade: up1 autoloads --8<---cut here---end--->8--- HTH Best, Martyn > Regards, > Achim.
Re: [O] orgstuct++ does not lurk silently in the shadow
Christopher Schmidt writes: > There is still one major issue, though. Consider this text: > > , > | >> rms > | >> foo > | >> > | >> org-mode > ` > > Place the point somewhere in the first or second line and do a M-q. > Vanilla message-mode correctly recognises the paragraph prefix whereas > an use of Org's enhancements breaks this. It all boils down to orgstruct++-mode setting non-org-vars like paragraph-start or paragraph-separate to the org values. This is fine, even the doc string says so. ,[ C-h f orgstruct++-mode RET ] | Toggle `orgstruct-mode', the enhanced version of it. | In addition to setting orgstruct-mode, this also exports all indentation | and autofilling variables from org-mode into the buffer. It will also | recognize item context in multiline items. ` This does not work with message-mode and any other mode that imposes a special document structure, though. I think the docstring and the manual should note that explicitly, and the line promoting the use of turn-on-orgstruct++ in message-mode-hook in (info "(org)Orgstruct mode") should be removed. Christopher
Re: [O] Org Clock Table / Subtree Export subtle bug
On Apr 29, 2012, at 7:49 AM, Mike McLean wrote: > > On Apr 28, 2012, at 7:19 PM, Bastien wrote: > >> The trick is to use (let ((delete-active-region nil)) ...) so that >> the active region is not deleted by such adjustments. > > Interesting, I was going to play a bit today and try things like > (save-excursion (deactivate-mark) … ) but didn't know if that was the right > approach or not. The delete-active-region sure seems simpler :) > >> I pushed a fix. > > Thank you I can confirm that the single-tree-export no longer corrupts the Org file and works with the EMF file. Strange though that now in my full setup the generated export does not include the Clock Report table. (This works fine with the test file in ~emacs -q~ so this is my issue).
Re: [O] Org Clock Table / Subtree Export subtle bug
On Apr 28, 2012, at 7:19 PM, Bastien wrote: > Hi Mike, > > thanks very much for the detailed bug report. > > Mike McLean writes: > >> The general symptom is that if: >> >>You have org-update-all-dblocks added >>to org-export-first-hook with the goal of ensuring that dynamic >>blocks are current before every export; AND >>You are exporting only a region of the file, for example >>using C-c C-e 1 b (buffer/subtree export) >> >> The Mark terminating the end of the region to be exported is carried >> into the org-clocktable-write-default formatting function and the >> call of (backward-delete-char 1) on line 2352 oforg-clock.el deletes >> a region (between the Mark of the initial call and point, which is >> immediately before the #+END: construct of the clock table). Deletion >> of the #+END: construct malforms the clock table and ultimately the >> export fails leaving the Org file is a corrupt state. > > The trick is to use (let ((delete-active-region nil)) ...) so that > the active region is not deleted by such adjustments. Interesting, I was going to play a bit today and try things like (save-excursion (deactivate-mark) … ) but didn't know if that was the right approach or not. The delete-active-region sure seems simpler :) > I pushed a fix. Thank you
Re: [O] notes in the agenda
Bastien writes: > Hi Richard, > > Richard Riley writes: > >> Now, whats the easist way to either (a, preferably) have the second agenda >> item display >> the *note* rather than the org item title > > There is no way to do this right now. > >> or (b, prefer not) remove it all together? > > I'd simply remove the timestamp from `org-log-note-headings', but I > guess you don't want that. > > Cheers, Thanks! While displaying the note (or start of the note...) itself in the agenda would be best (since notes are agenda/journal items in themselves), just replacing the %T with %t in the template for now avoids the duplicate agenda item.
Re: [O] orgstuct++ does not lurk silently in the shadow
Bastien writes: > This should be fixed now in master. Thank you so much for fixing this. There is still one major issue, though. Consider this text: , | >> rms | >> foo | >> | >> org-mode ` Place the point somewhere in the first or second line and do a M-q. Vanilla message-mode correctly recognises the paragraph prefix whereas an use of Org's enhancements breaks this. Other than that, disabling orgstruct++-mode after enabling it breaks everything. I get tons of "Lisp nesting exceeds `max-lisp-eval-depth'", even when doing simple things like moving around the buffer or trying to execute and extended command. For the record, I use Gnus and Org master (b5f4b52). This is how my integration is set up: #+begin_src emacs-lisp (add-hook 'gnus-message-setup-hook (lambda () (turn-on-orgtbl) (turn-on-orgstruct++) (set (make-local-variable 'org-footnote-auto-label) 'plain) (set (make-local-variable 'org-footnote-tag-for-non-org-mode-files) nil))) (define-key message-mode-map (kbd "C-c f") (lambda () (interactive) (save-restriction (my-message-narrow-to-body) (org-footnote-action (add-hook 'message-send-hook (lambda () (save-restriction (my-message-narrow-to-body) (org-footnote-normalize #+end-src Christopher
Re: [O] "Bad" interaction between flyspell and org-mode with latest Emacs
Hello, ** Bastien [2012-04-29 11:31:10 +0200]: > Hi Vladimir, > Vladimir Lomov writes: >> Emacs: bzr revno 108056 >> org-mode: 7.8.09-413-g21e24f @ /usr/share/emacs/site-lisp/org/org-install.el >> The same example file (~example.org~) and the same procecure to get >> "strange" behavior (I don't know how to explain it more precisely than >> that: run =C-c '= in src block, enter new line and immediately run =C-c >> '= again), but now there is not message in echo area about 'flyspell'. > [...] >> Revno 108011 is ok with this example. > So a more recent Emacs does not have this problem? Well, may be I said it too obscure, it is ok for revno <= 108011, but >= 10812 have problem. > Anyway, looks like it's more related to Emacs than to Org anyway... > I'm putting this out of my radar, maybe others might help. Sorry! I've already reported on bug#11351 (seems bug#9642 somehow related with this issue), but I'm not confident that it is the same issue. I'll send my reply to that thread. --- WBR, Vladimir Lomov -- Fashions have done more harm than revolutions. -- Victor Hugo
Re: [O] Capturing to current file
Hi Charles,
Charles writes:
> If I may I'll throw in my 2 cents, since I made the error in the first place
>
> Why not in Section 9.2.1 immediately before or after the "special way" for
> using capture from the agenda?
>
> The documentation reads as follows in org-capture.el at
>
> (defun org-capture (&optional goto keys)
> "Capture something.
> \\
>
> . . .
>
> When called with a `C-0' (zero) prefix, insert a template at point.
> . . .
I added this in 9.1.2:
To insert the capture at point in an Org buffer, call @code{org-capture} with
a @code{C-0} prefix argument.
Thanks for the suggestion!
--
Bastien
Re: [O] orgstuct++ does not lurk silently in the shadow
Hi Eric, Eric Fraga writes: > (add-hook 'message-setup-hook 'turn-on-orgstruct++) Try this instead, as advertized in the manual: (add-hook 'message-mode-hook 'turn-on-orgstruct++) HTH, -- Bastien
Re: [O] Navigating in sparse view from agenda?
Hi James, James Harkins writes: > Now, I would like to look up something under Audio 9 (hidden). But the > normal navigation commands don't find that item because it isn't > visible. I would simply use org-goto (`C-c C-j'), move to Audio 9, then hit RET. HTH, -- Bastien
Re: [O] "Bad" interaction between flyspell and org-mode with latest Emacs
Hi Vladimir, Vladimir Lomov writes: > Emacs: bzr revno 108056 > org-mode: 7.8.09-413-g21e24f @ /usr/share/emacs/site-lisp/org/org-install.el > > The same example file (~example.org~) and the same procecure to get > "strange" behavior (I don't know how to explain it more precisely than > that: run =C-c '= in src block, enter new line and immediately run =C-c > '= again), but now there is not message in echo area about 'flyspell'. > [...] > Revno 108011 is ok with this example. So a more recent Emacs does not have this problem? Anyway, looks like it's more related to Emacs than to Org anyway... I'm putting this out of my radar, maybe others might help. Sorry! -- Bastien
Re: [O] notes in the agenda
Hi Richard, Richard Riley writes: > Now, whats the easist way to either (a, preferably) have the second agenda > item display > the *note* rather than the org item title There is no way to do this right now. > or (b, prefer not) remove it all together? I'd simply remove the timestamp from `org-log-note-headings', but I guess you don't want that. Cheers, -- Bastien
Re: [O] Org Clock Timer in Frame Title bug
Hi George,
George Kettleborough writes:
> Checking (listp frame-title-format) ensures there will be no error when
> calling delq, but it doesn't fix the feature. If the user's
> frame-title-format is not a list then the feature will not work for no
> apparent reason. The same thing goes for global-mode-string too, which
> the current release of org-mode modifies.
>
> For the clock and timer display features to work as intended both of
> these variables need to be lists with either a string or a list as the
> first element. Note that simply being a list is not enough, it must
> contain a string or list as first element. This format causes the
> elements of the list to be treated as mode-line-formats recursively.
`global-mode-string' and ̀frame-title-format' are list by default
and they cannot be customized. They can be manually set to a string,
but that's a mistake (okay, `global-mode-string' is a misleading name.)
> The following in both org-clock.el and org-timer.el will ensure both
> variables have the correct format to begin with:
>
> (unless (and (listp frame-title-format)
> (or (stringp (first frame-title-format))
> (listp (first frame-title-format
> (setq frame-title-format (list "" frame-title-format)))
>
> (unless (and (listp global-mode-string)
> (or (stringp (first global-mode-string))
> (listp (first global-mode-string
> (setq global-mode-string (list "" global-mode-string)))
This can go into .emacs.el for those who set those two variables to a
string... but they should not do it in the first place, right?
> It might be better to do this just once in org.el or org-install.el,
> since maybe other modules might want to put stuff in the mode-line or
> frame-title.
>
> Of course the user or another mode might edit either of the variables to
> something bad (like a symbol or string) afterwards. Maybe this should
> be done every time before clock-in/timer-start or any time we wish to
> append stuff to either of these lists?
Org cannot fix all cases where the user is setting a variable to
something that is non-standard. For this issue, it's already nice
to not produce an error when the user set `global-mode-string' and
`frame-title-format' to "" instead of ("").
Or am I overlooking something?
--
Bastien
Re: [O] Symbol's value as variable is void: org-version
I pushed a fixed so that exporters won't fail at missing org-version. Achim and I are still working on this org-version issue, we will send a summary when it's done. Best, -- Bastien
Re: [O] Documentation vs. implementation for org-properties-postprocess-alist
Hi Bill, Bill Wishon writes: > While hacking around I read the doc for > org-properties-postprocess-alist and I think it doesn't align with > what the implementation of org-set-property does. I don't see anything wrong. Can you double-check? If there is a problem, please tell us what version of Org you are using. Thanks, -- Bastien
Re: [O] missing autoloads / (void-variable org-version)
Bastien writes: > Achim Gratz writes: > >> Bastien writes: >>> There is a fix that makes the new Makefile compatible with everyone's >>> configuration *without* requiring to add the version number directly in >>> the org.el file. I'm discussing it with Achim and will commit it as >>> soon as possible. >> >> Towards that end, I can test Emacs23 and Emacs24 on Linux. Anyone still >> using XEmacs and willing to check that everything keeps working there? > > Michael Sperber is our XEmacs fairy around, hopefully he we be able to > test the patch. Yes. I've also had to apply a few fixes to make the current XEmacs work. I intend to send a new batch of patches in two weeks or so, once everything has settled down on my end. (Until then, I'm quite swamped. If I don't answer e-mail in that timeframe, please don't assume I'm not interested.) -- Cheers =8-} Mike Friede, Völkerverständigung und überhaupt blabla
[O] notes in the agenda
Hi folks. I have a "journal template" which puts an active timestamp in journal entries so they appear in the default agenda. However the default note taking C-c C-z does this too. This is fine per-se but this means the note too appears in the agenda as shown here from the following org excerpt: , | *** 2012-04-29 Sunday | STARTED need to check Mike spoke with vodafone for 3g stick cancellation. | SCHEDULED: <2012-04-30 Mon> | :LOGBOOK: | - Note taken on <2012-04-29 Sun 11:32> \\ |Mike promised to call them night of the 28th April | :END: |:PROPERTIES: |:DateCreated: <2012-04-29 Sun 11:30> |:END: ` Agenda: , | Sunday 29 April 2012 |8:00.. | 10:00.. | Journal:11:30.. STARTED need to check Mike spoke with vodafone for 3g stick cancellation. | Journal:11:32.. STARTED need to check Mike spoke with vodafone for 3g stick cancellation. | 12:00.. now - - - - - - - - - - - - - - - - - - - - - - - - - ` Agenda bitmap: http://i.imgur.com/1j6dd.png Now, whats the easist way to either (a, preferably) have the second agenda item display the *note* rather than the org item title or (b, prefer not) remove it all together?
Re: [O] mail integration, advice?
Guys, very nice thread -- I can't wait to have a new computer (mine is a Thinkpad X61... nearly 5 years old!) and play with all this. Also nice to have Dirk on this list! Keep up the good work and let us know about other org/mu[4e] niceties. Cheers, -- Bastien
Re: [O] org-clocktable: Show timestamps for CLOCKED
Hi Moritz, Moritz Ulrich writes: > I'm currently running a report on my tasks last month. It works pretty > fine using the following clocktable invocation: > > #+BEGIN: clocktable :maxlevel 2 :scope subtree :compact t :timestamp t > #+END: > > This gives me a nice exportable clocktable for the current subtree > (which is what I've done for work last month). > > However, one thing isn't very nice. One (big) task was clocked over > two consecutive days: > > CLOCK: [2012-03-30 Fri 12:45]--[2012-03-30 Fri 18:25] => 5:40 > CLOCK: [2012-03-29 Thu 14:45]--[2012-03-29 Thu 19:11] => 4:26 > > org-clocktable's :timestamp doesn't handle this, showing the task > only with one timestamp in the table. This is as expected as the doc > says: "Look for SCHEDULED, DEADLINE, TIMESTAMP and TIMESTAMP_IA, in > this order.". > > I think org-clocktable should search for CLOCKED too. If you want two separate lines for the same entry, one for the time spent on the timestamp'ed day, another one for the time spent the next day, I think it would be confusing -- the (somewhat implicit) rule in the clocktable is to have one task per clocked item. Also, this would require internally processing CLOCK: lines that span over two days, and this is not trivial. But perhaps I'm misunderstanding. Can you provide an example? -- Bastien
Re: [O] Org tiny changes?
Hi François, François Pinard writes: > * It now seems that UNDER\_LINE, while producing HTML, is now rendering > the backslash instead of removing it. The backslash was previously > required so "LINE" is not shown as a subscript for "UNDER". Today, if > I use UNDER_LINE, it gets rendered as is, without the need of a > backslash. Can you give us a hint on what versions you're comparing here? > * Whenever a date is generated (through "C-c !" say) or adjusted, the > day of the week has a period appended. That is, where I was > previously getting "[2012-04-28 sam]", I now get "[2012-04-28 sam.]". IIRC, this is a change in calendar. But you don't need to update your old timestamps, Org understands them. > P.S. I installed Ubuntu 12.04 on a fresh partition today, and observed > the changes after the fact (and after having re-installed Org from Git). > This is probably a mere coincidence, I would not be tempted to think the > upgrading of Ubuntu has a consequence on the Org changes I'm seeing. Please give us raw version numbers. Thanks! -- Bastien
Re: [O] Google Summer of Code -- 3 Org projects for our first participation!
I Neil, Neil Smithline writes: > I think I'm lacking sufficient information to fully understand the > situation (that's just a secret code for saying I'm confused). here is a lengthy description for iOrg: http://orgmode.org/worg/org-contrib/gsoc2012/student-projects/bugpile/i.html This is just a *plan*, nothing is coded yet, and this plan might evolve as code will be written. HTH, -- Bastien
Re: [O] Google Summer of Code -- 3 Org projects for our first participation!
Hi Neil, Neil Smithline writes: > In the end, I think the way that the best way the list could help improve > Github's support of Org files would be to provide two things: > > 1) Come up with a prioritized list of features that would be nice to be > supported by Github. This may just be the most used features of Org Mode or > it may be something special to how Org Mode is used in Github. I'm not > sure. This is a good idea. We could start a page on Worg for this -- if you want to edit Worg, please send me your public key in private and I'll give you access. When you're done with a preliminary list of yours, perhaps inviting the github developers could boost both the brainstorming and the development of org-ruby. > 2) Have a few people look at the org-ruby gem and then brainstorm about the > best way to proceed. This would either require people who know Ruby or more > experienced software engineers. I modified the gem and learned Ruby by > reading the source for this gem and occasionally looking something up in a > reference manual. But I'd bet I've been coding longer than list members > such as Thorsten have been alive. If there are Ruby hackers around, that might work. But since org-ruby is widely used by a (big?) company like github, perhaps this company could lead such effort. > I really don't know enough about the culture of the Org Mode developers to > know if this is possible or not. The alternative is that I can just keep > adding features as I need them and think I can implement them. That would be nice. One thing to be aware of: there is an ongoing work by Nicolas to write a parser (see org-element.el in contrib/lisp/ from the git repo). It is already quite useful -- and used in the new exporters (e.g. org-e-latex.el) One nice side-effect of having this parser is that we will be able to document the syntax of Org files more clearly. Actually, org-element.el *is* such a description, but we need to make it widely available as a documentation page (on Worg). Thanks, -- Bastien
Re: [O] Some settings are missing while exporting included org files to the tex file
Keith writes: > Dear Org-mode users: > > Recently I am considering using org-mode to write my thesis and would > like to separate each chapter into a single file. In order to do so, I > created a file gathering all the rest files like this: [...] > In addition, I also tried to export a single org file without any > preamble to be able to use input/include in latex but with no luck. And > it seems org mode does not support this function yet. I would recommend > the development team to re-consider this feature. Now the tex output of > org mode draws all the separate files into single tex file and the user > has to compile the entire tex file every time. By doing so, it also > misses the feature of LaTex as mentioned here: > http://web.science.mq.edu.au/~rdale/resources/writingnotes/latexstruct.html > Keith, I cannot help you with the bulk of your email, regarding the use of #+include to bring in different chapters etc into a document and/or the possibility of working on each individual chapter in turn. However, because of these limitations, that I also ran into a long time ago, I simply put everything into one document. The advice given in the web page noted above is directed at LaTeX but is less necessary for org files. The motivation is the need or desire to work on smaller bits at a time to have things go quicker, I believe. The easy way to handle this in org is to use selective exporting, primarily through the use of tags. So, for instance, if I am working on a long document and am currently working on chapter 2 of this document, my document would look like this: , | ... | | #+EXPORT_SELECT_TAGS: export| | #+EXPORT_EXCLUDE_TAGS: noexport | | ... | | * Introduction ... :noexport: | | * Chapter 1 ... :noexport: | | * Chapter 2 | | ... | | * Chapter 3 ... :noexport: | | ... | ` When asking for an export, only Chapter 2 would be exported. It is trivial to add/remove the noexport tags. The only difficulty with this arises when you need latex material at the *end* of the document, such as bibliography settings. For this, I simply create a final "* Postamble" section which is exported. When my document is finished, I simply remove the heading line and re-export the whole document. A minor irritation appears if you have cross-references between chapters but that really is nothing more than an irritation so I have learnt to ignore it. HTH, eric -- : Eric S Fraga (GnuPG: 0xC89193D8FFFCF67D) in Emacs 24.1.50.1 : using Org release_7.8.09-414-gb3e8a8
Re: [O] mail integration, advice?
hi Neil > Are the directions at > http://www.djcbsoftware.nl/code/mu/mu4e/Gmail-configuration.html really > all it takes to get this running? If so, I'm definitely going to give it > a whirl. yes, check out that subsection for Gmail, or the earlier part of the manual for other configs. If you previously got mu working, and your email is under ~/Maildir you should find that something like: (add-to-list 'load-path "/usr/local/share/emacs/site-lisp/mu4e/") (autoload 'mu4e "mu4e" "Start mu4e" t) is all you need. Give it a go. If you liked mu, I think you'll like mu4e; Dirk's doing a great job! Stephen
