Re: [O] Bug: org-agenda-only-exact-dates [9.0.4 (9.0.4-elpa @ c:/Users/atamulis/.emacs.d/elpa/org-20170124/)]

2017-02-06 Thread Tamulis, Andrius
I tried it - it turns out that org-agenda-todo-ignore-deadlines only 
effects the global todo list.


Andrius

On 2017-02-06 07:17, Nicolas Goaziou wrote:

Hello,

"Tamulis, Andrius" <andri...@att.net> writes:


I had not read the docstring, but now I have, and I interpret it
differently than you did. As, it seems, did the people who coded it.
I want a zero value for org-deadline-warning-days, as I want no
warnings of future deadlines. But I also do not want notification of
deadlines that are past due, and that's not what
org-deadline-warning-days is for.

I was talking about `org-agenda-todo-ignore-deadlines' not
`org-deadline-warning-days'.

It would only apply to deadlines with a TODO keyword, tho.

Regards,






Re: [O] Bug: org-agenda-only-exact-dates [9.0.4 (9.0.4-elpa @ c:/Users/atamulis/.emacs.d/elpa/org-20170124/)]

2017-02-05 Thread Tamulis, Andrius
I had not read the docstring, but now I have, and I interpret it 
differently than you did. As, it seems, did the people who coded it. I 
want a zero value for org-deadline-warning-days, as I want no warnings 
of future deadlines. But I also do not want notification of deadlines 
that are past due, and that's not what org-deadline-warning-days is for.


Andrius

On 2017-02-04 13:58, Nicolas Goaziou wrote:

"Tamulis, Andrius" <andri...@att.net> writes:


The two variables you mention above fix almost everything for me - but
is there a "org-deadline-past-days" variable? Something that I could
set so that past due deadlines not be mentioned? Or may I suggest that
"org-agenda-todo-ignore-deadlines" have a value like "past", but one
that ignores deadlines that are in the past, but include those for
today.

Have you tried to set this variable to -1? According to the docstring,
it should do what you want. I didn't test it, tho.

Regards,





Re: [O] Bug: org-agenda-only-exact-dates [9.0.4 (9.0.4-elpa @ c:/Users/atamulis/.emacs.d/elpa/org-20170124/)]

2017-02-04 Thread Tamulis, Andrius

Thanks for the reply.

On 2017-02-03 16:16, Nicolas Goaziou wrote:

Hello,

"Tamulis, Andrius" <andri...@att.net> writes:


I note that in the latest version of orgmode, that the
org-agenda-only-exact-dates variable is no longer "honored". It is set
twice in org-agenda.el, but never checked, and so affects nothing.

When this functionality was deleted,

This variable is not documented in the manual. It has no docstring
either. I see no functionality here, only an obscure dynamically scoped
parameter.
If you search for org-agenda-exact-dates, you will find that I'm not the 
only one who has used this variable, and not the only one who has 
noticed its absence in version 9.

was any thought given to how one
may recreate the action of this variable? That is, in orgmode
9.0.4, how can I create an agenda that only shows entries whose exact
timestamp, scheduled or deadline, is the given day? And that ignores
"Sched. nx" and "In m d." entries?

I assume binding both `org-deadline-warning-days' and
`org-scheduled-past-days' to 0 would be a start. Also, you could bind
`org-agenda-span' to `day'.


The two variables you mention above fix almost everything for me - but 
is there a "org-deadline-past-days" variable? Something that I could set 
so that past due deadlines not be mentioned? Or may I suggest that 
"org-agenda-todo-ignore-deadlines" have a value like "past", but one 
that ignores deadlines that are in the past, but include those for 
today. Or does that variable only work with TODO lists, and not with 
agendas?


What I am trying to do is an agenda view in which only the tasks 
specifically for the given day - whether scheduled or deadline - appears.


Thanks,

Andrius



[O] Bug: org-agenda-only-exact-dates [9.0.4 (9.0.4-elpa @ c:/Users/atamulis/.emacs.d/elpa/org-20170124/)]

2017-02-02 Thread Tamulis, Andrius

I note that in the latest version of orgmode, that the
org-agenda-only-exact-dates variable is no longer "honored". It is set
twice in org-agenda.el, but never checked, and so affects nothing.

When this functionality was deleted, was any thought given to how one
may recreate the action of this variable? That is, in orgmode
9.0.4, how can I create an agenda that only shows entries whose exact
timestamp, scheduled or deadline, is the given day? And that ignores
"Sched. nx" and "In m d." entries?

Thank you,

Andrius

Emacs  : GNU Emacs 25.1.1 (x86_64-w64-mingw32)
 of 2016-11-15
Package: Org mode version 9.0.4 (9.0.4-elpa @ 
c:/Users/atamulis/.emacs.d/elpa/org-20170124/)





Re: [O] Bug: malformed property drawers [8.3.6 (8.3.6-3-gf46b92-elpa @ c:/Users/atamulis/.emacs.d/elpa/org-20160919/)]

2016-10-02 Thread Tamulis, Andrius
I hope this gets to the mailing list. I'm not sure how the mailing list 
works.


As for the below,
1) I've just spent a lot of time trying various searches at the 
emacs-orgmode Archives, and reading through many pages of results, but I 
can't find the mailing list discussion mentioned below by Nicolas. Can 
anyone help? Until I read that, I won't comment further on whether it 
was a good idea to insist that PROPERTIES and dates immediatly follow 
the headline.


2) If there is good code for fixing the properties drawers, why 
isn't it in the org-agenda-set-property function? The code there now 
just creates new PROPERTIES drawers, ignoring existing ones.


Thanks,

Andrius

On 2016-10-02 02:32, Nicolas Goaziou wrote:

Hello,

"Tamulis, Andrius" <andri...@att.net> writes:


There is a problem even if I want to "fix" these drawers by hand.
There are many, many drawers, and the fix is long and tedious:

It isn't. ORG-NEWS file provide a function to do the fixing for you.


I think that you should possible go back to the way it was before the
"fix the properties" patch. If it is terribly important to fix the
drawers, create a new function that fixes them as intelligently as
possible (copying existing drawers into the correct place).

See above.


But the better idea is to forget "fixing" these drawers. Is it truly
that important to have the SCHEDULED and DEADLINE in the line below
the heading, and the PROPERTIES drawer directly beneath?

Yes, it is. This subject was discussed on the ML already. Once fixed, it
is not much of an annoyance however.


Regards,






[O] Bug: malformed property drawers [8.3.6 (8.3.6-3-gf46b92-elpa @ c:/Users/atamulis/.emacs.d/elpa/org-20160919/)]

2016-10-01 Thread Tamulis, Andrius
I have a problem with orgmode related to the fixing of "malformed 
property drawers".


I use orgmode a lot; I have been using it for over a decade (if memory 
serves.) I use it to organize my life, my job, by volunteer work . My 
.org files are rather large - one is over 500 KB (that's for my job). I 
am having a problem with the (comparatively recent) change in the code 
that causes org-agenda-set-property (C-c C-x p) to search through the 
entire file looking for "malformed property drawers".


Over the years, my files have accumulated many, many property drawers 
that are not, strictly, in the correct place (which is supposed to be 
just below the SCHEDULED and DEADLINE line, right?). This used to not be 
a problem, then someone "fixed" the code, and now 
org-agenda-set-property tries to fix the drawers. And, unfortunatly, it 
"fixes" them by ignoring the drawer in the incorrect location and 
creating a new, empty one, not having carried over any properties.


There is a problem even if I want to "fix" these drawers by hand. There 
are many, many drawers, and the fix is long and tedious:


   C-c C-x p
   get the error message
   remember the character location
   C-g, M-x goto-char
   type character location
   hope that section has been unfolded (The fix searches inside
   ARCHIVEd locations!)
   check that the PROPERTY drawer does not have any important
   properties (except those left there by mobileorg)
   delete property drawer.

   Until {I get sick of it}

   C-c C-x P and type "CATEGORY:" myself, without the typing completion
   of C-c C-x p.


I think that you should possible go back to the way it was before the 
"fix the properties" patch. If it is terribly important to fix the 
drawers, create a new function that fixes them as intelligently as 
possible (copying existing drawers into the correct place).


But the better idea is to forget "fixing" these drawers. Is it truly 
that important to have the SCHEDULED and DEADLINE in the line below the 
heading, and the PROPERTIES drawer directly beneath? I see no 
programming advantage, since you need to search for these strings 
anyway. And I don't like the way it looks: I use org-mode to keep todo 
lists and notes, I need to read the notes and instructions I wrote to 
myself. These notes and instructions often are longer than the headline, 
so I naturally keep reading from the headline to the line below - and 
then I have to skip lines with code in them. And I'm not the only one 
who does not like this setup: there's code out there to completly hide 
the PROPERTIES drawer so that it does not interrupt your reading. 
(http://stackoverflow.com/questions/17478260/completely-hide-the-properties-drawer-in-org-mode). 



So: put SCHEDULED, DEADLINE, and drawers anywhere in the item! And stop 
fixing the drawers!


Thanks,

Andrius

Emacs  : GNU Emacs 24.5.1 (i686-pc-mingw32)
 of 2015-04-11 on LEG570
Package: Org-mode version 8.3.6 (8.3.6-3-gf46b92-elpa @ 
c:/Users/atamulis/.emacs.d/elpa/org-20160919/)




[O] Bug: org-table/auctex error "Marker does not point anywhere" [8.3.6 (8.3.6-3-gf46b92-elpa @ c:/Users/atamulis/.emacs.d/elpa/org-20160919/)]

2016-10-01 Thread Tamulis, Andrius
I get an error "Marker does not point anywhere" when using orgtbl-mode 
while using AUCTeX to edit a .tex file.


I open the .tex file, get to the table I want to edit, then do M-x 
orgtbl-mode. I then tab a couple of times. Then make an edit - any edit. 
Tab again, and the error comes up.


I finally traced the error to the line

   '(font-lock-global-modes nil)

in my .emacs file. Comment this out, and the error does not happen.

The error also does not happen if I rename the min.tex file to 
min.nottex, as then auctex does not recognize the file, and does not 
load. So this is a joint org-table/auctex/font-lock error, and I am 
submitting this bug to emacs-orgmode@gnu.org and to bug-auc...@gnu.org.


I really don't like font-lock, as I don't like all those colors. I'd 
prefer to have my font-lock-global-modes set to nil, somehow.


Minimal files and backtrace below.

Thanks,

Andrius

---

Files:

min.emacs:

---
(require 'package)
(add-to-list 'package-archives '("org" . "http://orgmode.org/elpa/;) t)
(package-initialize)

(setq debug-on-error t)

(custom-set-variables
 ;; custom-set-variables was added by Custom.
 ;; If you edit it by hand, you could mess it up, so be careful.
 ;; Your init file should contain only one such instance.
 ;; If there is more than one, they won't work right.
 '(font-lock-global-modes nil))

(require 'org-install)
(require 'org-table)

;; The following lines are always needed. Choose your own keys.
(global-set-key "\C-cl" 'org-store-link)
(global-set-key "\C-cc" 'org-capture)
(global-set-key "\C-ca" 'org-agenda)
(global-set-key "\C-cb" 'org-iswitchb)
---

and my min.tex:

---
\documentclass[%
12pt,%
%draft,%
%final,%
]{article}

\usepackage{comment}

\begin{document}

\begin{tabular}{|l|l|}
% BEGIN RECEIVE ORGTBL inclass
\hline
Score & Criteria\\
\hline
10 & Lorem ipsum dolor sit amet,\\
\hline
9 & consectetur adipiscing elit.\\
\hline
8 & Praesent eu arcu nisl.\\
\hline
7 & Aliquam sagittis aliquam iaculis.\\
\hline
6 & Proin dignissim, tellus sit amet faucibus fermentum,\\
\hline
5 & tellus tortor posuere justo,\\
0 & sit amet cursus eros felis ac lorem.\\
\hline
% END RECEIVE ORGTBL inclass
\end{tabular}
\begin{comment}
#+ORGTBL: SEND inclass orgtbl-to-latex :splice t :skip 0
|---+--|
| Score | Criteria |
|---+--|
|10 | Lorem ipsum dolor sit amet,  |
|---+--|
| 9 | consectetur adipiscing elit. |
|---+--|
|8  | Praesent eu arcu nisl.   |
|---+--|
| 7 | Aliquam sagittis aliquam iaculis.|
| 6 | Proin dignissim, tellus sit amet faucibus fermentum, |
| 5 | tellus tortor posuere justo, |
| 0 | sit amet cursus eros felis ac lorem. |
|---+--|
\end{comment}


\end{document}
---

And the backtrace:

---
Debugger entered--Lisp error: (error "Marker does not point anywhere")
  font-lock-default-fontify-region(537 # nil)
  font-latex-fontify-region(537 # nil)
  font-lock-fontify-region(537 #)
  org-table-align()
  org-table-next-field()
  orgtbl-tab(nil)
  call-interactively(orgtbl-tab)
  (if (org-at-table-p) (call-interactively (quote orgtbl-tab)) (let 
(orgtbl-mode) (call-interactively (or (key-binding [(tab)]) (key-binding 
"") (quote orgtbl-error)

  orgtbl-hijacker-command-102(1)
  call-interactively(orgtbl-hijacker-command-102 nil nil)
  command-execute(orgtbl-hijacker-command-102)
---


Emacs  : GNU Emacs 24.5.1 (i686-pc-mingw32)
 of 2015-04-11 on LEG570
Package: Org-mode version 8.3.6 (8.3.6-3-gf46b92-elpa @ 
c:/Users/atamulis/.emacs.d/elpa/org-20160919/)

AUCTeX Package: 11.89.5