Re: [O] org-babel (org-babel-detangle)
Eric Schulte schulte.eric at gmail.com writes: Hi Mohamed, The comment prompt you mentioned actually isn't babel specific but is raised by the `comment-region' function which is used by babel to comment out links. Look at the documentation for `comment-region' (below) which has information on variables to set to avoid the comment syntax prompt in xml documents. Best -- Eric ,[C-h f comment-region] | comment-region is an interactive compiled Lisp function in | `newcomment.el'. | | It is bound to C-c r. | | (comment-region BEG END optional ARG) | | Comment or uncomment each line in the region. | With just C-u prefix arg, uncomment each line in region BEG .. END. | Numeric prefix ARG means use ARG comment characters. | If ARG is negative, delete that many comment characters instead. | | The strings used as comment starts are built from `comment-start' | and `comment-padding'; the strings used as comment ends are built | from `comment-end' and `comment-padding'. | | By default, the `comment-start' markers are inserted at the | current indentation of the region, and comments are terminated on | each line (even for syntaxes in which newline does not end the | comment and blank lines do not get comments). This can be | changed with `comment-style'. ` Mohamed HIBTI mohamed.hibti at gmail.com writes: Eric Schulte schulte.eric at gmail.com writes: Hi Eric, I tried it, it worked quite well but I have a trouble with the syntax comment (No comment syntax is defined. Use: ) Since I have too many blocks, is there any way to set it as a local variable ? Regards, Mohamed P.S. I tried without success #+ Local Variables : #+ org-babel-tangle-comment-format-beg: !--[[%link][source-name]] #+ org-babel-tangle-comment-format-end: source-name ends here-- #+ End: and # Local Variables : # org-babel-tangle-comment-format-beg: !--[[%link][source-name]] # org-babel-tangle-comment-format-end: source-name ends here-- # End: Thanks for this answer. You are right ! In the line #+BEGIN_SRC XML :tangle ./sample04.xml :comment yes XML (with capitals) is not identified with the xml-mode where the variables `comment-begin' and `comment-end' are well defined. I changed to #+BEGIN_SRC xml :tangle ./sample04.xml :comment yes and it worked ! Best regards, Mohamed Thanks for this answer. You are right ! In the line #+BEGIN_SRC XML :tangle ./sample04.xml :comment yes XML (with capitals) is not identified with the xml-mode where the variables `comment-begin' and `comment-end' are well defined. I changed to #+BEGIN_SRC xml :tangle ./sample04.xml :comment yes and it worked ! Best regards, Mohamed
Re: [O] org-babel (org-babel-detangle)
Eric Schulte schulte.e...@gmail.com writes: Thanks for this answer. I got it. Hi Mohamed, The comment prompt you mentioned actually isn't babel specific but is raised by the `comment-region' function which is used by babel to comment out links. Look at the documentation for `comment-region' (below) which has information on variables to set to avoid the comment syntax prompt in xml documents. Best -- Eric ,[C-h f comment-region] | comment-region is an interactive compiled Lisp function in | `newcomment.el'. | | It is bound to C-c r. | | (comment-region BEG END optional ARG) | | Comment or uncomment each line in the region. | With just C-u prefix arg, uncomment each line in region BEG .. END. | Numeric prefix ARG means use ARG comment characters. | If ARG is negative, delete that many comment characters instead. | | The strings used as comment starts are built from `comment-start' | and `comment-padding'; the strings used as comment ends are built | from `comment-end' and `comment-padding'. | | By default, the `comment-start' markers are inserted at the | current indentation of the region, and comments are terminated on | each line (even for syntaxes in which newline does not end the | comment and blank lines do not get comments). This can be | changed with `comment-style'. ` Mohamed HIBTI mohamed.hi...@gmail.com writes: Eric Schulte schulte.eric at gmail.com writes: Hi Eric, I tried it, it worked quite well but I have a trouble with the syntax comment (No comment syntax is defined. Use: ) Since I have too many blocks, is there any way to set it as a local variable ? Regards, Mohamed P.S. I tried without success #+ Local Variables : #+ org-babel-tangle-comment-format-beg: !--[[%link][source-name]] #+ org-babel-tangle-comment-format-end: source-name ends here-- #+ End: and # Local Variables : # org-babel-tangle-comment-format-beg: !--[[%link][source-name]] # org-babel-tangle-comment-format-end: source-name ends here-- # End:
Re: [O] org-babel (org-babel-detangle)
Eric Schulte schulte.eric at gmail.com writes: Hi Eric, I tried it, it worked quite well but I have a trouble with the syntax comment (No comment syntax is defined. Use: ) Since I have too many blocks, is there any way to set it as a local variable ? Regards, Mohamed P.S. I tried without success #+ Local Variables : #+ org-babel-tangle-comment-format-beg: !--[[%link][source-name]] #+ org-babel-tangle-comment-format-end: source-name ends here-- #+ End: and # Local Variables : # org-babel-tangle-comment-format-beg: !--[[%link][source-name]] # org-babel-tangle-comment-format-end: source-name ends here-- # End:
Re: [O] org-babel (org-babel-detangle)
Hi Mohamed, The comment prompt you mentioned actually isn't babel specific but is raised by the `comment-region' function which is used by babel to comment out links. Look at the documentation for `comment-region' (below) which has information on variables to set to avoid the comment syntax prompt in xml documents. Best -- Eric ,[C-h f comment-region] | comment-region is an interactive compiled Lisp function in | `newcomment.el'. | | It is bound to C-c r. | | (comment-region BEG END optional ARG) | | Comment or uncomment each line in the region. | With just C-u prefix arg, uncomment each line in region BEG .. END. | Numeric prefix ARG means use ARG comment characters. | If ARG is negative, delete that many comment characters instead. | | The strings used as comment starts are built from `comment-start' | and `comment-padding'; the strings used as comment ends are built | from `comment-end' and `comment-padding'. | | By default, the `comment-start' markers are inserted at the | current indentation of the region, and comments are terminated on | each line (even for syntaxes in which newline does not end the | comment and blank lines do not get comments). This can be | changed with `comment-style'. ` Mohamed HIBTI mohamed.hi...@gmail.com writes: Eric Schulte schulte.eric at gmail.com writes: Hi Eric, I tried it, it worked quite well but I have a trouble with the syntax comment (No comment syntax is defined. Use: ) Since I have too many blocks, is there any way to set it as a local variable ? Regards, Mohamed P.S. I tried without success #+ Local Variables : #+ org-babel-tangle-comment-format-beg: !--[[%link][source-name]] #+ org-babel-tangle-comment-format-end: source-name ends here-- #+ End: and # Local Variables : # org-babel-tangle-comment-format-beg: !--[[%link][source-name]] # org-babel-tangle-comment-format-end: source-name ends here-- # End: -- Eric Schulte http://cs.unm.edu/~eschulte/
[O] org-babel (org-babel-detangle)
Dear all, I have a problem with detangling org-babel fragments. May be this is because XML is not a supported feature/or I use it in a wrong way. Any help is welcome. My org-file is below. I can tangle this file to obtain the XML file but when I try to jump to org I get the message not in tangled code. *** TODO Question that needs validation :PROPERTIES: :ID: 2788f65d-5613-40c1-80ae-ae966f4bb398 :END: #+BEGIN_SRC XML :tangle ./sample04.xml :comment yes define-fault-tree name=ACP-2 !-- Le problème de cette question -- ! labelAC Power System Bus 2/label define-gate name=@ACP-2-1 code:calctype=Q labelAC Power System Bus 2 fails/label and gate name=@ACP-2-2/ gate name=@ACP-2-3/ /and /define-gate /define-fault-tree #+END_SRC Best regards, Mohamed
Re: [O] org-babel (org-babel-detangle)
Hi Mohamed, You have a small typo in your header arguments, :comment should be :comments. After that change then code block should be tangled wrapped in comments, and then Babel can use these comments to jump back to the original org-mode file. That said, the detangle mechanisms are in need of some work, specifically regarding their use of the Org-mode's link resolution, which doesn't currently make it possible to programmatically jump to the results of a link. So, until some time is spent fixing up the detangling machinery inside of Babel, you may not find detangling to be extremely robust. Best -- Eric Mohamed HIBTI mohamed.hi...@gmail.com writes: Dear all, I have a problem with detangling org-babel fragments. May be this is because XML is not a supported feature/or I use it in a wrong way. Any help is welcome. My org-file is below. I can tangle this file to obtain the XML file but when I try to jump to org I get the message not in tangled code. *** TODO Question that needs validation :PROPERTIES: :ID: 2788f65d-5613-40c1-80ae-ae966f4bb398 :END: #+BEGIN_SRC XML :tangle ./sample04.xml :comment yes define-fault-tree name=ACP-2 !-- Le problme de cette question -- ! labelAC Power System Bus 2/label define-gate name=@ACP-2-1 code:calctype=Q labelAC Power System Bus 2 fails/label and gate name=@ACP-2-2/ gate name=@ACP-2-3/ /and /define-gate /define-fault-tree #+END_SRC Best regards, Mohamed -- Eric Schulte http://cs.unm.edu/~eschulte/
Re: [O] org-babel (org-babel-detangle)
Eric Schulte schulte.e...@gmail.com writes: Hi Eric, Thanks for this swift reply. I will try :) Best regards, Mohamed Hi Mohamed, You have a small typo in your header arguments, :comment should be :comments. After that change then code block should be tangled wrapped in comments, and then Babel can use these comments to jump back to the original org-mode file. That said, the detangle mechanisms are in need of some work, specifically regarding their use of the Org-mode's link resolution, which doesn't currently make it possible to programmatically jump to the results of a link. So, until some time is spent fixing up the detangling machinery inside of Babel, you may not find detangling to be extremely robust. Best -- Eric Mohamed HIBTI mohamed.hi...@gmail.com writes: Dear all, I have a problem with detangling org-babel fragments. May be this is because XML is not a supported feature/or I use it in a wrong way. Any help is welcome. My org-file is below. I can tangle this file to obtain the XML file but when I try to jump to org I get the message not in tangled code. *** TODO Question that needs validation :PROPERTIES: :ID: 2788f65d-5613-40c1-80ae-ae966f4bb398 :END: #+BEGIN_SRC XML :tangle ./sample04.xml :comment yes define-fault-tree name=ACP-2 !-- Le problme de cette question -- ! labelAC Power System Bus 2/label define-gate name=@ACP-2-1 code:calctype=Q labelAC Power System Bus 2 fails/label and gate name=@ACP-2-2/ gate name=@ACP-2-3/ /and /define-gate /define-fault-tree #+END_SRC Best regards, Mohamed
