Re: [O] Bug: `comment-line` within a SRC block moves point to beginning of block [9.2 (9.2-43-gf9a8cc-elpaplus)]

2019-01-30 Thread kadal 

I have the same issue with:

Org mode version 9.2 (9.2-43-gf9a8cc-elpaplus)
GNU Emacs 27.0.50 (build 2, x86_64-pc-linux-gnu, GTK+ Version 3.18.9) of 
2018-12-14


I assumed it was a bug in comment-dwim-2, but it occurs with 
comment-line too.


On 1/30/19 1:13 PM, Nicolas Goaziou wrote:

Hello,

Spencer Russell  writes:


Thanks for trying it out. Would you mind sharing your emacs and org
versions?


Sure.

Org mode version 9.2 (release_9.2-213-g5c07b4)
GNU Emacs 26.1

Could you try master branch?

Regards,

Re: [O] org-return does not work in magit's git-commit-setup-hook

2018-03-18 Thread kadal 

OK. Thanks. I've switched to Orgalist.

On 03/17/2018 02:21 AM, Nicolas Goaziou wrote:

Hello,

kadal <kadalcaly...@gmail.com> writes:


I have the line (add-hook 'git-commit-setup-hook 'orgstruct++-mode)
but (org-return) does not work when edting the commit message.


`orgstruct-mode' does not exist anymore in master branch (i.e., yet to
be released Org 9.2). I suggest to just remove this hook.

Regards,

[O] org-return does not work in magit's git-commit-setup-hook

2018-03-15 Thread kadal 
I have the line (add-hook 'git-commit-setup-hook 'orgstruct++-mode) but 
(org-return) does not work when edting the commit message.


This is the backtrace:

"Debugger entered--Lisp error: (wrong-type-argument stringp nil)
  looking-at(nil)
  org-return()
  (cond ((eq 'line-break (car (org-element-context))) 
(org-return-indent)) ((or (and (eq 'link (car (org-element-context))) 
(not (eolp))) (bolp)) (org-return)) ((org-inlinetask-in-task-p) 
(org-return)) ((org-at-item-checkbox-p) (cond ((and (eolp) (not (eq 
'item (car (org-element-context) (org-insert-todo-heading nil)) 
((and (eolp) (eq 'item (car (org-element-context (let* ((v 
(line-beginning-position)) (v (point))) (cl--set-buffer-substring v v 
""))) ((eq 'paragraph (car (org-element-context))) (goto-char 
(org-element-property :end (org-element-context))) 
(org-insert-todo-heading nil)) (t (org-return ((org-in-item-p) (cond 
((and (looking-at " ::") (looking-back "- " 3)) (beginning-of-line) 
(delete-region (line-beginning-position) (line-end-position))) ((and 
(looking-at "$") (looking-back "- " 3)) (beginning-of-line) 
(delete-region (line-beginning-position) (line-end-position))) ((and 
(looking-at "$") (looking-back "[0-9]*. " (line-beginning-position))) 
(beginning-of-line) (delete-region (line-beginning-position) 
(line-end-position))) (t (end-of-line) (org-insert-item 
((org-at-heading-p) (if (not (string= "" (org-element-property :title 
(org-element-context (progn (org-end-of-subtree) 
(org-insert-heading-respect-content) (outline-show-entry)) 
(beginning-of-line) (let* ((v (line-beginning-position)) (v 
(line-end-position))) (cl--set-buffer-substring v v "" 
((org-at-table-p) (if (-any\? (function (lambda (x) (not (string= "" 
x (nth (- (org-table-current-dline) 1) (remove 'hline 
(org-table-to-lisp (org-return) (beginning-of-line) (let* ((v 
(line-beginning-position)) (v (line-end-position))) 
(cl--set-buffer-substring v v "")) (org-return))) (t (org-return)))
  (if ignore (org-return) (cond ((eq 'line-break (car 
(org-element-context))) (org-return-indent)) ((or (and (eq 'link (car 
(org-element-context))) (not (eolp))) (bolp)) (org-return)) 
((org-inlinetask-in-task-p) (org-return)) ((org-at-item-checkbox-p) 
(cond ((and (eolp) (not (eq 'item (car (org-element-context) 
(org-insert-todo-heading nil)) ((and (eolp) (eq 'item (car 
(org-element-context (let* ((v (line-beginning-position)) (v 
(point))) (cl--set-buffer-substring v v ""))) ((eq 'paragraph (car 
(org-element-context))) (goto-char (org-element-property :end 
(org-element-context))) (org-insert-todo-heading nil)) (t 
(org-return ((org-in-item-p) (cond ((and (looking-at " ::") 
(looking-back "- " 3)) (beginning-of-line) (delete-region 
(line-beginning-position) (line-end-position))) ((and (looking-at "$") 
(looking-back "- " 3)) (beginning-of-line) (delete-region 
(line-beginning-position) (line-end-position))) ((and (looking-at "$") 
(looking-back "[0-9]*. " (line-beginning-position))) (beginning-of-line) 
(delete-region (line-beginning-position) (line-end-position))) (t 
(end-of-line) (org-insert-item ((org-at-heading-p) (if (not (string= 
"" (org-element-property :title (org-element-context (progn 
(org-end-of-subtree) (org-insert-heading-respect-content) 
(outline-show-entry)) (beginning-of-line) (let* ((v 
(line-beginning-position)) (v (line-end-position))) 
(cl--set-buffer-substring v v "" ((org-at-table-p) (if (-any\? 
(function (lambda (x) (not (string= "" x (nth (- 
(org-table-current-dline) 1) (remove 'hline (org-table-to-lisp 
(org-return) (beginning-of-line) (let* ((v (line-beginning-position)) (v 
(line-end-position))) (cl--set-buffer-substring v v "")) (org-return))) 
(t (org-return"

Re: [O] ox-html export bug

2017-09-08 Thread kadal 

On 09/08/2017 10:32 AM, Nicolas Goaziou wrote:

kadal <kadalcaly...@gmail.com> writes:


Seems like the second one should export to either ""
or "".


Is it valid HTML?

Regards,

This SO thread has confusing answers: 
https://stackoverflow.com/questions/192048/can-an-html-element-have-multiple-ids#192066


Looks like the second option will work. That said, the first option is 
better because if I'm setting a CUSTOM_ID, that's what should be used 
for internal links...


Deepak

Re: [O] ox-html export bug

2017-09-08 Thread kadal 



Fair point.  Would it be sufficient to give these type of links a class,
say "org-internal-links".  Then you should be able to explicitly turn off
the content for these links.

 .org-internal-links::after {content:"";}


I don't know, looks like a bug to me.


I haven't put much thought into it, but I wonder if it would be possible
to ignore EXTRA-IDS and only use PREFERRED-ID (see `org-html-headline'),
i.e., use

   (or (org-element-property :CUSTOM_ID headline)
   (org-export-get-reference headline info))

It could be a problem when publishing to HTML, but I'm not sure at this
point.


Going back to the original report:

--

1 heading 1



2 heading 2



---

The first headline with no CUSTOM_ID exports to ""
The second headline with a CUSTOM_ID exports to "id="orge4e91c4">"


Seems like the second one should export to either "" or 
"". Not sure why the empty link is 
being inserted or needs to be there at all.


Deepak

Re: [O] ox-html export bug

2017-09-07 Thread kadal 
The problem is that if you have CSS that decorates links by adding 
content after a link, that (empty) link gets decorated too.


Is it possible to remove it? There is no such empty link for the first 
heading which does not have CUSTOM_ID set.


Deepak

On 09/07/2017 10:32 AM, Nicolas Goaziou wrote:

Hello,

kadal <kadalcaly...@gmail.com> writes:


This org file

-
* heading 1
* heading 2
:PROPERTIES:
:CUSTOM_ID: my-name
:END:



exports to

---

1 heading 1



2 heading 2



---

The "" for the second heading is unnecessary.
Seems to only occur when CUSTOM_ID is set.


It is the internal reference for "my-name" custom ID.

Regards,

[O] ox-html export bug

2017-09-07 Thread kadal 

This org file

-
* heading 1
* heading 2
:PROPERTIES:
:CUSTOM_ID: my-name
:END:



exports to

---

1 heading 1



class="section-number-2">2 heading 2




---

The "" for the second heading is unnecessary. 
Seems to only occur when CUSTOM_ID is set.


Deepak