[O] "C-M" showing up everywhere in the INFO file

Hi, I'm using the lasted org-mode from git, I used make install info to generate the INFO file and I have verified that the file "org" has been copied to the "info" directory of my emacs directory. I'm using Windows, and the problem is that "C-M" is appearing everywhere in this INFO file which is

[O] "org-sort" doesn't work properly on active region

Hi, When using "org-sort" on a selected region, it doesn't work properly, I expected it to sort all the headlines in the region, however, not only does the region get sorted but also, the headlines get sorted are being combinded into one line which I don't think is correct. Hopefully somebody will

[O] Fwd: "org-sort" doesn't work properly on active region

>> When using "org-sort" on a selected region, it doesn't work properly, I >> expected >> it to sort all the headlines in the region, however, not only does the region >> get sorted but also, the headlines get sorted are being combinded into one >> line >> which I don't think is correct. Hopefull

Re: [O] "org-sort" doesn't work properly on active region

> 4) I still cannot reproduce the problem, even with latest git. It turns out that this was my own configuration problem and not a bug, I apologize for the false report and appreciate Nick's help. Thanks, York

Re: [O] "org-sort" doesn't work properly on active region

> an ECM is a minimal example file: a small org file that shows the problem, as > small as you can make it and still have it show the problem. Thanks Nick

[O] "org-time-stamp" and "org-time-stamp-inactive" no longer work

Hi, I have noticed this problem for awhile and now I think it is worth reporting it and hopefully get fixed. Here is what happened when I hit "C-c !" in org buffer: Debugger entered--Lisp error: (wrong-type-argument window-live-p nil) select-window(nil) org-eval-in-calendar(nil t) byte-cod

Re: [O] "org-time-stamp" and "org-time-stamp-inactive" no longer work

> What is your version of Emacs and Org-mode? Emacs v23.3.1 on Windows, Org-mode version 7.7 (release_7.7.625.gf18b1) Thanks, York

Re: [O] "org-time-stamp" and "org-time-stamp-inactive" no longer work

> Does that version exist? I just pulled and I get > > Org-mode version 7.7 (release_7.7.624.gda56) I guess it should be (release_7.7.624.gda56) then because I always have one commit ahead of the latest which is for my local Makefile configuration. Every time I pulled, I rebased my commit. Sorry f

Re: [O] "org-time-stamp" and "org-time-stamp-inactive" no longer work

> > Matt reported a similar problem in > > > > But it seems the problem just ... fixed itself: > > , > | However, oddly, after experiencing the same issue about 6 times in a > | row, the problem mysteriously disappeared just now, a

Re: [O] "org-time-stamp" and "org-time-stamp-inactive" no longer work

>> Matt reported a similar problem in >> >> >> >> But it seems the problem just ... fixed itself: >> >> , >> | However, oddly, after experiencing the same issue about 6 times in a >> | row, the problem mysteriously disappeared just

Re: [O] "org-time-stamp" and "org-time-stamp-inactive" no longer work

>> To keep this list updated, I just upgraded to the latest Emacs from git, >> compiled and linked using mingw and this problem no longer exists. Thank you >> all >> for your help and merry Christmas. > > Thanks for the update! > > -- >  Bastien You are welcome Bastien and Merry Christmas. York

[O] LaTeX export

Hi there, I'm wondering if there is a way to export ONLY the LaTeX code within "#+begin_latex" and "#+end_latex". I want the exact literal export without adding anything before and after my code. The result should be exactly the same as if I have copied the block between "#+begin_latex" and "#+end

Re: [O] LaTeX export

> I would use code blocks tangling > > , > | #+TITLE: Test > | > | * Test headline > | > | #+begin_src tex :tangle yes > | \documentclass{article} > | \begin{document} > | ... > | \end{document} > | #+end_src > ` > > `C-c C-v t' on the block will create a .tex file with the exact content >

Re: [O] LaTeX export

> Read Chapter 14 of the Org-mode manual. And go to > http://orgmode.org/worg/ and search with the keyword "literate". Thanks, I've read these already, they are helpful. Happy New Year York

[O] Feature suggestion

Hi, May I suggest a feature that when the point is inside a TeX source block and "C-c C-c" is pressed, instead of showing the error "No org-babel-execute function for tex!", can we process the current tex block to output the dvi or pdf file? Thanks, York

Re: [O] Feature suggestion

> York Zhao writes: > >> May I suggest a feature that when the point is inside a TeX source block and >> "C-c C-c" is pressed, instead of showing the error "No org-babel-execute >> function for tex!", can we process the current tex block to output the

Re: [O] still seeing semi-regular lockups

My experience of using `org-mode' (git commit "2824502" and previous versions) with Emacs 24.3.91 (git commit "0f0917d") had been a nightmare. I got bitten by this bug frequently, I was mad. Some of my `org-drill' entires might have been damaged to some extent. This was a problem with Emacs 24.3.1

Re: [O] still seeing semi-regular lockups

> Yeah, I'm using git emacs, labeled 24.4.50.1 Did you compile Emacs from git? I have never seen the tag 24.4.50.1, are you sure you didn't have a typo here? On Sat, Jun 28, 2014 at 10:23 PM, Eric Abrahamsen wrote: > York Zhao writes: > >> My experience of using `org-m

Re: [O] still seeing semi-regular lockups

duces error: "Variable bind exceeds maximum level" or something. A few hours ago I switched back to Emacs 24.3.1, problem 1 happened once, but never had problem 2. And editing in `org-mode' was several times more smooth and faster. Way better. Again, I want to stress, I was using the sam

[O] Wrong numbering after removal of headline

Hi list, As an example, I have the follow org-mode buffer: * Level1 ** Level2 *** Level3 If I export this to LaTeX (C-x C-e l p), it produces the following: --8<---cut here---start->8--- Contents 1 Level1 1.1 Level2 . . . . . . . . . . . . . . . . . . . . .

Re: [O] Wrong numbering after removal of headline

> You could promote the Level2 subtree. I had thought about this, but I don't think this will be trivial. On Mon, Jun 30, 2014 at 3:37 PM, Thomas S. Dye wrote: > Aloha York, > > York Zhao writes: > >> Hi list, >> >> As an example, I have the follow org-mo

Re: [O] Wrong numbering after removal of headline

;m getting the error: "org-map-tree: Symbol's value as variable is void: org-called-with-limited-levels". Any idea? Thanks On Mon, Jun 30, 2014 at 5:38 PM, Nicolas Goaziou wrote: > Hello, > > York Zhao writes: > >> As an example, I have the follow org-mode buf

Re: [O] Wrong numbering after removal of headline

Finally, I got it all work and am happy with the result, here is the code: (defun yz/org-export-ignore-headline (backend) "Ignore headlines with tag `ignoreheading'." (save-excursion (let ((org-allow-promoting-top-level-subtree t)) (org-map-entries (lambda () (when (m

[O] Force new page on exporting

I'm selectively exporting some subtree of an org-mode buffer, like this: * Headline1 :export: * Headline2 * Headline3 :export: Question is: how do I force Headline3 to be on a new pag

Re: [O] Force new page on exporting

d have to remember to move the "\newpage" to the end of the new tree. On Mon, Jun 30, 2014 at 8:49 PM, Thomas S. Dye wrote: > Aloha York, > > York Zhao writes: > >> I'm selectively exporting some subtree of an org-mode buffer, like this: >> >> * Headline1

Re: [O] Force new page on exporting

> * Latex New Page :ignoreheading: > #+latex: \newpage This should work, but didn't, I will figure out why when I have some time. > Also, see the LaTeX commands \pagebreak and \clearpage, which do generally the > same thing but in slightly different ways. I was aware of these, but if \newpage do

Re: [O] Force new page on exporting

> My understanding is that you need extra machinery to implement "ignoreheading" I had implemented machinery the "ignoreheading" and posted the code in the post "Wrong numbering after removal of headline". But anyways here's my code: (defun yz/org-export-process-heading-removal (backend) "Ignor

Re: [O] Force new page on exporting

> So before parsing, you are getting rid of the "ignoreheading" headline (first, > "promoting" it to a comment and then deleting the region), so the #+latex: > \newpage line now belongs to headline 2 which is then parsed and discarded. Really great catch Nick, exactly as what you pointed out. Save

Re: [O] still seeing semi-regular lockups

> Please update, if you can. I pushed a couple of fixes a few hours ago. It may > solve the problem. I noticed the new commits after my previous report. I'm now using commit "126e2bc", this morning I did experience some funny things which I had never experienced before. Unfortunately I let them go

Re: [O] Force new page on exporting

OK, hacked `org-export-filter-headline-functions' and added the facility to force exporting a headline on new page by adding a new tag "newpage" to the headline. Here is the code: (defun yz/org-export-headline-on-new-page (contents backend info) "Export headlines with tag `newpage' on new pages.

Re: [O] still seeing semi-regular lockups

Just suffered from extreme slowness. My Emacs had been running for about 1 hour and I was having two org-mode buffers, one file has 3800 lines, 168 KB bytes. And the other has 76,600 lines, 4,267,327 KB bytes. Both files had been opened for awhile. Didn't have problem in the beginning, but then typ

Re: [O] still seeing semi-regular lockups

> OK. If you experience it again, please do > > M-x org-element-cache-reset > > in the slow buffer and see if it is responsive again. > > Another interesting test would be to try reproducing the problem with > `org-element-use-cache' set to nil. The exact same slowness problem happened just now.

Re: [O] still seeing semi-regular lockups

> I'm now using commit "126e2bc", this morning I did experience some funny > things which I had never experienced before. Unfortunately I let them go. I > will keep an eye on the new problems. I'm now using commit "fdc673d". The problem I experienced 2 days ago happened again. The direct operation

Re: [O] still seeing semi-regular lockups

> I'm now using commit "fdc673d". The problem I experienced 2 days ago happened > again. The direct operations I did was that I programmatically deleted a few > table line in one table and inserted them in another table which is in the > subtree immediately following the current table. But I ended

Re: [O] Force new page on exporting

Thought I should post an update to fix a regexp problem, hopfully somebody else will find it useful. (defun yz/org-export-headline-on-new-page (contents backend info) "Export headlines with tag `newpage' on new pages." (when (org-export-derived-backend-p backend 'latex) (with-temp-buffer

Re: [O] still seeing semi-regular lockups

> Thank you for the report. I wasn't able to reproduce it with latest commit > (df9ccbd). Could you try again and see if it fixes your problem? I haven't experienced this problem since July 3, hopefully it has been fixed. Thank you very much for your work. York

Re: [O] still seeing semi-regular lockups

> > The exact same slowness problem happened just now. "M-x org-element-cache-reset" > > didn't have any effect. Nor did setting `org-element-use-cache' to nil. Again, > > killed the buffer and reopened didn't help. > It looks like the problem isn't related to the cache then. Anyway, you > could tr

[O] Indentation messed up after example block

Hi list, I just noticed a problem that org-mode indentation gets messed up after "example" block. Here is ECM: #+STARTUP: indent * Level one ** Level two Indentation is right. #+BEGIN_EXAMPLE * Example at level one #+END_EXAMPLE Indentation is wrong.

Re: [O] still seeing semi-regular lockups

The extreme slowness happened again just know. When this happened, `org-end-of-line' command took forever until "C-g". M-x org-element-cache-reset worked this time, i.e., after running `org-element-cache-reset' command `org-end-of-line' became fast again. I was using commit "ca6ecf9", and the buff

Re: [O] still seeing semi-regular lockups

> Could you send me the document you were working on, in private, and describe > what you were doing before it froze? I'm sorry but I really shouldn't send this document to anyone other than a lawyer :-) > or at least an equivalent file structure wise, calling the following function > in that doc

Re: [O] still seeing semi-regular lockups

> > The exact same slowness problem happened just now. "M-x org-element-cache-reset" > > didn't have any effect. Nor did setting `org-element-use-cache' to nil. Again, > > killed the buffer and reopened didn't help. > It looks like the problem isn't related to the cache then. Anyway, you > could tr

Re: [O] still seeing semi-regular lockups

>> + zfill-org-paragraph-boundary 7,240 0% > What is that, if I may ask? That's in my `zfill-mode' based on `refill-mode', and the function is part of the machinery to handle the automatic refilling of org paragraph. > + ac-handle-post-command

Re: [O] Indentation messed up after example block

>> Hi list, >> >> I just noticed a problem that org-mode indentation gets messed up after >> "example" block. Here is ECM: >> >> #+STARTUP: indent >> >> * Level one >> ** Level two >> Indentation is right. >> >> #+BEGIN_EXAMPLE >> * Example at level one >> #+END_EXAMPLE >> >> Indentation is wrong.

[O] Issue with multiple references to the same footnote in LaTeX export

If I have multiple references to the same footnote, in LaTeX export only the first reference is a clickable link, the rest are exported as dead number referring to the footnote definition, but not clickable links. I have `org-footnote-section' set to `nil' by the way. Here's ECM: --8<

Re: [O] Issue with multiple references to the same footnote in LaTeX export

Any one? On Wed, Jul 9, 2014 at 2:07 PM, York Zhao wrote: > If I have multiple references to the same footnote, in LaTeX export only > the > first reference is a clickable link, the rest are exported as dead number > referring to the footnote definition, but not clickable links. I

Re: [O] Issue with multiple references to the same footnote in LaTeX export

Hi list, I'm re-posting this again because I just noticed that I shouldn't have copied the "Local Variables". Now it is a smaller ECM. If I have multiple references to the same footnote, in LaTeX export only the first reference is a clickable link, the rest are exported as dead number referring t

Re: [O] still seeing semi-regular lockups

> On Mon, Jun 30, 2014 at 8:43 PM, York Zhao wrote: > I got the problem today, with org-mode version "815c218" in Emacs 24.3.1. The > error message is: if: Lisp nesting exceeds `max-lisp-eval-depth'. Attached is > the backtrace saved in a file. Hope this will help.

Re: [O] still seeing semi-regular lockups

> FWIW, I'm still getting regular lockups with the cache. I'll dig into it > further when I have time. I'm still being locked up from time to time, maybe less than before I guess. What I said was that I never got the deadly problem of "Lisp nesting exceeds `max-lisp-eval-depth", and the fix had be

Re: [O] Extremely slow org-table operations

Thanks On Wed, Oct 29, 2014 at 5:43 AM, Nicolas Goaziou wrote: > Hello, > > York Zhao writes: > >> A few months ago I tried Emacs 24.4 and was disappointed because almost all >> of >> the org-table operations became AT LEAST ten times slower. Because recently >&g

Re: [O] Extremely slow org-table operations

right? Please confirm. York On Wed, Oct 29, 2014 at 7:40 PM, Charles Millar wrote: > Hi, > > > York Zhao wrote: > >> I think Org 8.3 should improve the situation. Please test it if you can. >>> >> I was aware that my "emacs -Q" test was done agains

Re: [O] Extremely slow org-table operations

really doesn't make sens that it has to be slow. Needlessly to say that `org-mode' is fantastic, but with this issue, I have to say that `org-mode' is unhealthy. Therefore, I really hope this issue gets addressed. Please let me know what I can do to help. Thanks in advance, Yor

[O] `org-drill' broken in recent commits git commits

Hi there, `org-drill' has broken recently (after git commit "3380460"), here is the steps to reproduce the issue: 1. Create a new org-mode buffer with the following contents: * org-drill test :drill: Foo ** Answer Bar 2. M-x org-drill 3. Press 4. Press `2' and you are stuck there forever until

Re: [O] `org-drill' broken in recent commits git commits

#x27; hasn't been changed for a few months. When you test `org-drill' on the sample file have you been asked to input a date? Thanks, York On Sat, Feb 16, 2013 at 9:38 AM, Bastien wrote: > Hi York, > > York Zhao writes: > >> Hi there, `org-drill' has broken r

Re: [O] `org-drill' broken in recent commits git commits

Hi Bastien, I have figured out that I could press "S-arrow" to change the date when being asked to input a date after selected '2'. I found that if I change it to a future date I will not be asked for this question in the current drill session because the scheduled date has been set to a future da

[O] org-capture with function type target

Hi list, I'm been so frustrated when trying to use function as `target' in an org-capture' template, here is my example: 1. Create a file "~/test.org" and add a line "* Level 1", make sure to add a newline character after the inserted line 2. Set org-capture-template as: (setq org-capture-templat

Re: [O] org-capture with function type target

To whom it may concern, Please find attached my patch to address this issue. Please let me know if the patch is acceptable. Thanks, York On Sat, Nov 16, 2013 at 8:13 PM, York Zhao wrote: > Hi list, > > I'm been so frustrated when trying to use function as `target'

[O] commit 5ea0228 has problem opening big org-mode file

Hi List, I have an org-mode file that is 3230004 bytes in size. With commit "92f30ae" it can be opened without any problem. However, with commit "5ea0228" the same file could not be opened properly. What I did was: I opened Dired buffer, select the file, press enter, nothing happened and Emacs lo

Re: [O] commit 5ea0228 has problem opening big org-mode file

Oop, I didn't know that I replied to Nicolas instead of to the list because I hitted "reply" instead of "reply all". So I'm reposting my previous post to the list. Here we go: In my previous post I actually meant to say that I set `debug-on-quit', have no idea why I did `debug-on-error'. But anywa

Re: [O] commit 5ea0228 has problem opening big org-mode file

e, first, you have to make two files, .emacs and "yhj-mode.el". Second, this line must be present: (add-to-list 'load-path "path/to/org-mode/lisp") ; this line is the key Third, file "yhj-mode.el" has to be byte-compiled. York On Mon, Nov 25, 2013 at 5:39 PM,

Re: [O] commit 5ea0228 has problem opening big org-mode file

> York Zhao writes: >> (add-to-list 'load-path "path/to/org-mode") > > This line is not needed. My org-mode is "installed" in separate directory outside of Emacs system and therefor this line is needed in my setup, otherwise the org-mode shipped with Ema

Re: [O] commit 5ea0228 has problem opening big org-mode file

> Can both interested parties (York Zhao and Tom Dye) please test it and let me > know of any problems? Thank you for the fix, your patch worked for me. York

Re: [O] org-capture with function type target

Hi Carsten, Thank you. York

Re: [O] commit 5ea0228 has problem opening big org-mode file

> The only path that needs to be in load-path is the lisp directory for > org-mode, which is the second line (that you say is "key"). You are right on this which I didn't realize before you pointed out, thanks. Anyways, in my configuration I always have both lines, and I'm going to delete the firs

Re: [O] commit 5ea0228 has problem opening big org-mode file

> It could have (depending on what other files you might have had there, > not from the Git repo). May happen in theory, but never in real life, at least never happen on me. > It certainly muddied the waters w.r.t. your bug report. I had provided a reproducer proved to be straightforward and eff

[O] Intermixed date in koma-letter export

Let's say I have two letters: * Letter1 ** Preamble :noexport: #+DATE: 2015-10-26 Monday ** To whom it may concern, * Letter2 ** Preamble :noexport: #+DATE: 2015-12-03 Thursday ** Hi, No matter whether I select letter1, or letter2, run `org-export-dispatch' and choose to export k

Re: [O] Intermixed date in koma-letter export

n, Dec 7, 2015 at 4:21 AM, Rasmus wrote: > York Zhao writes: > > > Let's say I have two letters: > > > > * Letter1 > > ** Preamble :noexport: > > > > #+DATE: 2015-10-26 Monday > > ** To whom it may concern, > > > > >

Re: [O] Intermixed date in koma-letter export

date is still "Dec 12, 2015". Hope this helps,\\ York On Thu, Dec 10, 2015 at 10:45 AM, Rasmus wrote: > Hi, > > York Zhao writes: > > > Thanks for your help. However, adding the :EXPORT_DATE: property doesn't > > work. Firstly, there's an error:

Re: [O] Intermixed date in koma-letter export

part of the buffer will be exported. Anyway, glad that I've got a solution! Thanks,\\ York On Fri, Dec 11, 2015 at 6:44 PM, Nicolas Goaziou wrote: > Hello, > > York Zhao writes: > > > I selected the "letter 1" subtree, pressed C-cekp, opened the pdf file. > But

Re: [O] Intermixed date in koma-letter export

> Anyway, glad that I've got a solution! Unfortunately, I've just noticed that the "C-s" subtree export also exported the heading (the "letter1" in my example), which is definitely unacceptable when exporting a letter. On Fri, Dec 11, 2015 at 9:55 PM, York Zh

Re: [O] Intermixed date in koma-letter export

orks the same as the "title" option, and has exactly the same problem. Thanks On Sat, Dec 12, 2015 at 5:39 AM, Rasmus wrote: > Hi, > > York Zhao writes: > > >> Anyway, glad that I've got a solution! > > > > Unfortunately, I've just noti

Re: [O] Intermixed date in koma-letter export

here? Thanks, York On Sat, Dec 12, 2015 at 1:13 PM, Rasmus wrote: > York Zhao writes: > > >> #+options: title:nil > > > > Thanks a lot! This worked, but still problematic. If I have "#+options: > > title:centered" for letter 1 but "#+options: titl

Re: [O] Intermixed date in koma-letter export

erties. Have no idea why I didn't see them before. Thanks a lot! Thanks, York On Sun, Dec 13, 2015 at 11:29 AM, Rasmus wrote: > Hi, > > York Zhao writes: > > >> Use the :EXPORT_OPTIONS: subheading options. > > > > Thanks a lot, this really worked. I'm

[O] How to export casual letter without from and to address?

Hi list, I've been wondering for a while that when using org-mode to write letters, how do you export casual a letter that doesn't have from address and to address? Thanks in advance, York

Re: [O] How to export casual letter without from and to address?

Please share how you write notes (casual letter without "from address" and "to address") in Emacs org-mode, print out and give to somebody. Thanks,\\ York On Fri, Mar 4, 2016 at 12:12 AM, York Zhao wrote: > Hi list, > > I've been wondering for a while that wh

Re: [O] How to export casual letter without from and to address?

nt class. Obviously you can't use "article", nor "book". So my question may probably rephrase as: which latex document class do you use to export the letter "as is"? Thanks, York On Sat, Mar 5, 2016 at 5:12 AM, Eric S Fraga wrote: > On Friday, 4 Mar 2016 at 22

Re: [O] How to export casual letter without from and to address?

ks, York On Sat, Mar 5, 2016 at 6:22 AM, H. Dieter Wilhelm wrote: > Eric S Fraga writes: > >> On Friday, 4 Mar 2016 at 22:36, York Zhao wrote: >>> Please share how you write notes (casual letter without "from address" and >>> "to >>> address&qu

[O] koma letter export receiver address

Dear org-mode koma letter developers, I just noticed that when using org koma letter export, the receiver's address has been moved from left side to page center. Is this the new default or an introduced bug? If it's the new default, how do I change it back to the old behavior? Thanks, York

Re: [O] How to export casual letter without from and to address?

,\\ York On Sun, Mar 6, 2016 at 2:04 PM, Rasmus wrote: > York Zhao writes: > >> Hi list, >> >> I've been wondering for a while that when using org-mode to write letters, >> how >> do you export casual a letter that doesn't have from address and to a

Re: [O] koma letter export receiver address

3.3 (release_8.3.3-640-g2b3c72 @ /usr/local/share/emacs/site-lisp/org/) Please find attach the file "test.org" and "test.pdf" produced by hitting C-c C-e C-s k o. Thanks, York On Sun, Mar 6, 2016 at 2:06 PM, Rasmus wrote: > York Zhao writes: > >> Dear org-mode ko

Re: [O] koma letter export receiver address

Just wanted to follow up with this issue. I just tested it with the latest org-mode (git commit 7e320e2), the problem was still there. Any chance this can be addressed? Thanks, York On Sun, Mar 6, 2016 at 8:34 PM, York Zhao wrote: > Hi Rasmus, > > Thanks for your help. Here&#x

Re: [O] koma letter export receiver address

e two files again with this post. Hope this helps. Thanks, York On Fri, Apr 22, 2016 at 5:51 AM, Rasmus wrote: > Hi, > > York Zhao writes: > > > Just wanted to follow up with this issue. I just tested it with the > latest > > org-mode (git commit 7e320e2), the problem w

Re: [O] koma letter export receiver address

Sorry Rasmus, but I don't understand what you are talking about. Have you sent to a wrong subject? Thanks, York On Sat, Apr 23, 2016 at 9:18 AM, Rasmus wrote: > Hi, > > Can you just change the template to DIN or must you use the French format? > E.g.: > > #+LCO: DIN > > Rasmus > > -- > Nee

Re: [O] koma letter export receiver address

ajority of the users are from the English world, I believe! Just a suggestion. Thanks, York On Sat, Apr 23, 2016 at 10:18 AM, Rasmus wrote: > York Zhao writes: > > > Sorry Rasmus, but I don't understand what you are talking about. Have you > > sent to a wrong subject? >

Re: [O] html to org-mode

Hi John Kitchin, What is org-rss, I couldn't find it. Can you give a link? Thanks On Fri, Jan 3, 2014 at 11:56 PM, Feng Shu wrote: > John Kitchin writes: > > > Hi everyone, > > > > I was playing around with org-rss today, and it is pretty cool. I > > would like to customize the way the sub

[O] (org-insert-headline '(4)) should insert new headline before point

Hi list, (org-insert-headline '(4)) used to insert new heading before point. But this had broken recently. According to the docstring, this command inserts new heading at the end of the parent subtree ONLY if two universal prefix arguments is given, not one. Here's the reproducer: --8<--

Re: [O] (org-insert-headline '(4)) should insert new headline before point

Any one? On Thu, Apr 3, 2014 at 6:59 PM, York Zhao wrote: > Hi list, > > (org-insert-headline '(4)) used to insert new heading before point. But this > had > broken recently. According to the docstring, this command inserts new > heading at the end of the parent subtree

Re: [O] Prepare release 8.2.6

Hi there, I reported a regression a few days ago, and I just knew that you are busy preparing a new release. Since the bug I reported is a regression, I think you may want to consider fix it before releasing the new version. Here's the bug report I copied from the other email I had sent to this li

[O] Patch to fix `org-test-with-temp-text'

refor, I will appreciate it if this patch can be taken care of as soon as possible. Thank you, York From 9bbfc37ab059e923c57eaa99e3a2d81144c80218 Mon Sep 17 00:00:00 2001 From: York Zhao Date: Wed, 9 Apr 2014 13:39:16 -0400 Subject: [PATCH] testing/org-test.el (org-test-with-temp-text): Fix po

[O] Patch for testing `org-open-at-point'

x27;t place the test in the wrong file. York From df0788134a16baa9762616637c0fe7f568e3e63e Mon Sep 17 00:00:00 2001 From: York Zhao Date: Thu, 10 Apr 2014 21:21:15 -0400 Subject: [PATCH] test-org-element: Add test for `org-open-at-point' with link being heading property. --- testing/lisp

Re: [O] Patch for testing `org-open-at-point'

dd tests when they don't fail :) Fair enough, just make sure it will not be forgotten. Thanks On Fri, Apr 11, 2014 at 6:25 AM, Bastien wrote: > Hi York, > > York Zhao writes: > >> I found a bug that `org-open-at-point' doesn't work if the link is a >> headi

Re: [O] Patch for testing `org-open-at-point'

is hardly useful because too often the web link is really long, in which case the bracket link acts like a way of abstraction. Thank you very much for considering this fix. On Thu, Apr 17, 2014 at 2:48 PM, Bastien wrote: > Hi York, > > York Zhao writes: > >> * Peter >> :PR

Re: [O] (org-insert-headline '(4)) should insert new headline before point

de, if you replace `(forward-line)' in the test with `(forward-line -1)' (moving to previous line) the test will pass, which means that the new heading had been inserted after the current heading, not before. Let me know if this is still not clear. Thanks, York On Thu, Apr 17, 2014

Re: [O] Patch for testing `org-open-at-point'

14 at 3:56 PM, York Zhao wrote: > Hi Bastien, > > I apologize that I missed your reply, I discovered it until now when I was > checking the replies in the "Sent" folder. > >> The question is this: are we fine handling raw links in properties, >> or do we also

[O] Document of org-map-entries

Hi list, I wanted to know how to use the MATCH parameter in `org-map-entries'. I've searched extensively, but was unable to find much useful information. Can somebody please shed some lights on this? Thanks, York

Re: [O] Document of org-map-entries

at 12:46 AM, Nick Dokos wrote: > York Zhao writes: > > > > I wanted to know how to use the MATCH parameter in > > `org-map-entries'. I've searched extensively, but was unable to find > > much useful information. Can somebody please shed some lights on > &

Re: [O] Document of org-map-entries

One more question: how do I map only the entries that has a specific property defined? The following code didn't work. (org-map-entries (lambda () (...)) "mytag+myproperty<>nil") Thanks, On Thu, Oct 13, 2016 at 1:00 AM, York Zhao wrote: > Thank you very mu

Re: [O] Document of org-map-entries

syntax works: * Tree :PROPERTIES: :myproperty: :END: But there's probably no point to have such empty property after all. So you approach is acceptable. Thanks! Regards, York On Thu, Oct 13, 2016 at 11:57 AM, Nick Dokos wrote: > York Zhao writes: > > > Thank you very muc

[O] `org-store-link' to skip link storing functions without touching `org-context-in-file-links'

Hi org-mode developers, Recently I found it very useful to being able to store links linking to source code in git repository. I used org-git-link.el for this purpose and it works well. However, the biggest problem I'm having now is that once I loaded org-git-link.el, I'm forced to always store l

Re: [O] `org-store-link' to skip link storing functions without touching `org-context-in-file-links'

017 at 6:55 PM, Kyle Meyer wrote: > York Zhao writes: > > > However, the biggest problem I'm having now is that once I loaded > > org-git-link.el, I'm forced to always store links linking to git > repository > > which is not always I want because I also need to