Re: [O] scale inline images in orgmode

2015-02-24 Thread Shavkat Rustamov
Hello,

This setting works fine:

(setq org-image-actual-width 300)

  = always resize inline images to 300 pixels

However, this does not {it falls back to 400 and ignores #+ATTR}:

(setq org-image-actual-width '(400))

  = if there is a #+ATTR.*: width=200, resize to 200,
 otherwise resize to 400

I tried different versions of #+ATTR, including:

##+ATTR.*: :width 150px
##+ATTR.*: width=100
##+ATTR_HTML: :width 300px
#+ATTR_HTML: :width=100

Any idea what’s wrong?


[O] (org-use-fast-tag-selection (quote auto)) - non ASCII characters shown as e.g. [\200] and other problems

2015-02-16 Thread Shavkat Rustamov
I have set up only one persistent tag set with a key character like this:
(org-tag-persistent-alist (quote ((@i_shopping . 105

There are no file based #+TAGS in any of org files.

I also like to have access to all tags in all files, so I set this up:
(org-complete-tags-always-offer-all-agenda-tags t)

Finally I'd like to have a fast selection splash screen:
(org-use-fast-tag-selection (quote auto))

Now the problems:
Running C-q in an org file on a heading shows a fast selection splash
window:
1. The main problem is that the assigned fast pick characters are not only
'a-z',  but also non-ASCII characters which are shown as:
- [\200] tagname1
- [\204] tagname2
- etc
There seems to be no way to select tagname1 or tagname2.

2. With all the above variables unchanged hitting the TAB here for
selection of tags in the minibuffer only allows tags already in the file,
ignoring the (org-complete-tags-always-offer-all-agenda-tags t) variable.
Disabling (org-use-fast-tag-selection (quote auto)) and hitting TAB after
C-q actually shows the selection of all tags in a Completions buffer as
expected, except in the Capture Buffer.

3. In a Capture Buffer, in addition to problem 1., and problem 2.,  TAB
does not show a full list of tags in the Completions buffer (with the
disabled fast select as in Problem 2. above).  However, typing a first
letter of a tag and then TAB will list all tags beginning with that letter
in all the org files and not only org-tag-persistent-alist.

So, fast select seems broken.

I would expect it  behave like this:

1. having (org-complete-tags-always-offer-all-agenda-tags t) and
(org-use-fast-tag-selection
(quote auto)) should limit the tags selection to ASCII only characters or
offer double character selection like [aa]-[zz] if there are more tags that
az permits. Use numbers perhaps too?.

2. If 1. is not possible then perhaps limit the characters to az and
leaving other tags out of the fast select but allow TAB to choose all tags
in all org files using org-ido?

3. what is the point of 'auto' in  (org-use-fast-tag-selection (quote
auto)) if it does exactly the same thing if set to  (org-use-fast-tag-selection
(quote always))?

I'm forced currently to disable (org-use-fast-tag-selection (quote auto))
 setting it to  (org-use-fast-tag-selection (quote never)) and use the
Completions buffer, which seems to work more consistently.


[O] (org-use-fast-tag-selection (quote auto)) - problem with TAB Completion and non ASCII tag selection characters [\200]

2015-02-13 Thread Shavkat Rustamov
I have
​
one
​
persistent tag
​
​
set with a key character like this:
 '(org-tag-persistent-alist (quote ((a . 97

There are no file based #+TAGS in any of org files.

I also like to have access to all tags in all files, so I set this up:
(org-complete-tags-always-offer-all-agenda-tags t)

Finally I'd like to have a fast selection splash screen:
(org-use-fast-tag-selection (quote auto))

Now the problems:

​1. ​
Running C-q in an org file on a heading shows a fast selection splash window
​. ​
​
​
It shows all the tags from all the org files.
​
The main problem is that

apart from [a] defined in org-tag-persistent-alist other characters are
​
assigned
​
for
​
 fast pick
​
randomly
​
and
​
are not only 'a-z',  but also

seemingly
​
non-ASCII characters which are shown as:
- [\200] tagname1
- [\204] tagname2
- etc
There seems to be no way to select tagname1 or tagname2.

2. With all the above variables unchanged hitting the TAB here for
selection of tags in the minibuffer only allows tags already in the file,
ignoring the (org-complete-tags-always-offer-all-agenda-tags t) variable.
Disabling
​
'
​
org-use-fast-tag-selection
​
' by setting it
​

to

'nil'
​
 and hitting TAB after C-q
produces ':' and the Completions buffer is not opened. However, typing a
first character of a tag, say 'b' and hitting TAB opens 'Completions'
buffer and lists all tags starting with 'b'
​
.

Note that org ido completion (which would be shown as 'Ido Completions'
buffer name) is not used although  (org-completion-use-ido t) if
(org-use-fast-tag-selection (quote
​
nil
​
))
​
.
​


3.
​I
​
n addition to problem 1., and problem 2., TAB does not show a full list of
tags in the Completions buffer
​
which start with 'a' {probably due to the tag 'a'
​
defined above}, but selecting another starting letter and hitting TAB opens
Completion buffer with all tags starting with 'b'
​
.

So, fast select seems broken.

I would expect it behave like this:

1. having (org-complete-tags-always-offer-all-agenda-tags t) and
(org-use-fast-tag-selection (quote auto)) should limit the tags selection
to ASCII only characters or offer double character selection like [aa]-[zz]
if there are more tags that az permits. Use numbers perhaps too?.
2. If 1. is not possible then perhaps limit the characters to
​
'
​
a
​
-
​
z
​
'
​
 and leaving other tags out of the fast select but allow TAB to choose all
tags in all org files using org-ido?

I'm forced currently to disable (org-use-fast-tag-selection (quote auto))
 setting it to  (org-use-fast-tag-selection (quote
​
nil
​
)) and use the Completions buffer, which
​
seems to work more consistently.


[O] org-mobile-push: Non-existent .#flagged.org angenda - how to avoid this message?

2014-08-13 Thread Shavkat Rustamov
When calling org-mobile-push, org gives this message Non-existing agenda
file .#flagged.org.

.# are lock files (create-lockfiles variable), which get created in the org
directory. I would prefer to have them.