Re: [O] Tags completion with Helm

[aaermolov]

followup:

Further debugging revealed that helm-hide-minibuffer-maybe is not guilty
of anything. But for some reason, helm-mode-fuzzy-match /
helm-completion-in-region-fuzzy-match fix the problem, but only using 2+
chars queries. Maybe some other customizations are responsible for that.


aaermo...@gmail.com writes:

> Yes, with some some config fiddling I've seen this crm-based tagging
> wotkflow you describe, but problems were the same.
>
> Suddenly, I tried to remove some customization code for Helm (namely
> this -
> https://github.com/search?q=helm-hide-minibuffer-maybe=Code=✓)
> and it seems proper completion starts working to some extent.
>
> Anyway, thanks for prompt reply and mind seeding! :)
>
>
> John Kitchin  writes:
>
>> I can't reproduce that behavior on my end. I see different behavior though.
>> My helm window is titled crm-complete, and the buffer is called
>> *helm-mode-crm-complete*
>>
>> This seems to be the helm core package I am using.
>>
>> helm-core-20170112.917
>>
>> John
>>
>> ---
>> Professor John Kitchin
>> Doherty Hall A207F
>> Department of Chemical Engineering
>> Carnegie Mellon University
>> Pittsburgh, PA 15213
>> 412-268-7803
>> @johnkitchin
>> http://kitchingroup.cheme.cmu.edu
>>
>>
>> On Tue, Mar 14, 2017 at 12:24 PM,  wrote:
>>
>>> Hi John,
>>>
>>> no, these do not seem to fix anything. :(
>>>
>>> Namely, the following is still happens:
>>>
>>> 1) I'm pressing C-c C-q then TAB to select freeform input
>>> 2) then there is "org-set-tags" above candidates list and buffer title
>>>is "*helm-mode-org-set-tags*"
>>> 3) after any input candidates list looks like "[?]"
>>>(initial candidates disappeared)
>>>
>>> regards,
>>> Alex
>>>
>>> John Kitchin  writes:
>>>
>>> > have you tried these settings:
>>> >
>>> > (setq helm-mode-fuzzy-match t
>>> >   helm-completion-in-region-fuzzy-match t)
>>> >
>>> > According to https://github.com/emacs-helm/helm/wiki/Fuzzy-matching, the
>>> > make fuzzy matching work everywhere.
>>> >
>>> > It seems to work ok for me.
>>> >
>>> > aaermo...@gmail.com writes:
>>> >
>>> >> Hi,
>>> >>
>>> >> I've spotted a problem with completing Org tags with Helm. While Helm is
>>> >> not at least about [fuzzy] completion, when I try to input any
>>> >> completion subsequence, all candidates are gone and variants are
>>> >> shrinked to whatever will be typed.
>>> >>
>>> >> Is there any widely known mistake, that I've stepped into with this
>>> >> case? Can anyone point me to some comprehensible direction?
>>> >>
>>> >> regards,
>>> >> Alex
>>> >
>>> >
>>> > --
>>> > Professor John Kitchin
>>> > Doherty Hall A207F
>>> > Department of Chemical Engineering
>>> > Carnegie Mellon University
>>> > Pittsburgh, PA 15213
>>> > 412-268-7803
>>> > @johnkitchin
>>> > http://kitchingroup.cheme.cmu.edu
>>>


signature.asc
Description: PGP signature

Re: [O] Tags completion with Helm

[aaermolov]

Yes, with some some config fiddling I've seen this crm-based tagging
wotkflow you describe, but problems were the same.

Suddenly, I tried to remove some customization code for Helm (namely
this -
https://github.com/search?q=helm-hide-minibuffer-maybe=Code=✓)
and it seems proper completion starts working to some extent.

Anyway, thanks for prompt reply and mind seeding! :)


John Kitchin  writes:

> I can't reproduce that behavior on my end. I see different behavior though.
> My helm window is titled crm-complete, and the buffer is called
> *helm-mode-crm-complete*
>
> This seems to be the helm core package I am using.
>
> helm-core-20170112.917
>
> John
>
> ---
> Professor John Kitchin
> Doherty Hall A207F
> Department of Chemical Engineering
> Carnegie Mellon University
> Pittsburgh, PA 15213
> 412-268-7803
> @johnkitchin
> http://kitchingroup.cheme.cmu.edu
>
>
> On Tue, Mar 14, 2017 at 12:24 PM,  wrote:
>
>> Hi John,
>>
>> no, these do not seem to fix anything. :(
>>
>> Namely, the following is still happens:
>>
>> 1) I'm pressing C-c C-q then TAB to select freeform input
>> 2) then there is "org-set-tags" above candidates list and buffer title
>>is "*helm-mode-org-set-tags*"
>> 3) after any input candidates list looks like "[?]"
>>(initial candidates disappeared)
>>
>> regards,
>> Alex
>>
>> John Kitchin  writes:
>>
>> > have you tried these settings:
>> >
>> > (setq helm-mode-fuzzy-match t
>> >   helm-completion-in-region-fuzzy-match t)
>> >
>> > According to https://github.com/emacs-helm/helm/wiki/Fuzzy-matching, the
>> > make fuzzy matching work everywhere.
>> >
>> > It seems to work ok for me.
>> >
>> > aaermo...@gmail.com writes:
>> >
>> >> Hi,
>> >>
>> >> I've spotted a problem with completing Org tags with Helm. While Helm is
>> >> not at least about [fuzzy] completion, when I try to input any
>> >> completion subsequence, all candidates are gone and variants are
>> >> shrinked to whatever will be typed.
>> >>
>> >> Is there any widely known mistake, that I've stepped into with this
>> >> case? Can anyone point me to some comprehensible direction?
>> >>
>> >> regards,
>> >> Alex
>> >
>> >
>> > --
>> > Professor John Kitchin
>> > Doherty Hall A207F
>> > Department of Chemical Engineering
>> > Carnegie Mellon University
>> > Pittsburgh, PA 15213
>> > 412-268-7803
>> > @johnkitchin
>> > http://kitchingroup.cheme.cmu.edu
>>


signature.asc
Description: PGP signature

Re: [O] Tags completion with Helm

[aaermolov]

Hi John,

no, these do not seem to fix anything. :(

Namely, the following is still happens:

1) I'm pressing C-c C-q then TAB to select freeform input
2) then there is "org-set-tags" above candidates list and buffer title
   is "*helm-mode-org-set-tags*"
3) after any input candidates list looks like "[?]"
   (initial candidates disappeared)

regards, 
Alex

John Kitchin  writes:

> have you tried these settings:
>
> (setq helm-mode-fuzzy-match t
>   helm-completion-in-region-fuzzy-match t)
>
> According to https://github.com/emacs-helm/helm/wiki/Fuzzy-matching, the
> make fuzzy matching work everywhere.
>
> It seems to work ok for me.
>
> aaermo...@gmail.com writes:
>
>> Hi,
>>
>> I've spotted a problem with completing Org tags with Helm. While Helm is
>> not at least about [fuzzy] completion, when I try to input any
>> completion subsequence, all candidates are gone and variants are
>> shrinked to whatever will be typed.
>>
>> Is there any widely known mistake, that I've stepped into with this
>> case? Can anyone point me to some comprehensible direction?
>>
>> regards,
>> Alex
>
>
> --
> Professor John Kitchin
> Doherty Hall A207F
> Department of Chemical Engineering
> Carnegie Mellon University
> Pittsburgh, PA 15213
> 412-268-7803
> @johnkitchin
> http://kitchingroup.cheme.cmu.edu


signature.asc
Description: PGP signature

[O] Tags completion with Helm

[aaermolov]

Hi,

I've spotted a problem with completing Org tags with Helm. While Helm is
not at least about [fuzzy] completion, when I try to input any
completion subsequence, all candidates are gone and variants are
shrinked to whatever will be typed. 

Is there any widely known mistake, that I've stepped into with this
case? Can anyone point me to some comprehensible direction?

regards,
Alex


signature.asc
Description: PGP signature

Re: [O] Literate config and :tangle clauses

[aaermolov]

Hi, Chuck

I do not blame Org at first place, but I've bisected my config and the
behaviour is the same for a significant list of commits deeper in git
history. And, as I've already mentioned, it started to behave as
described only some time ago (about a week), after one of the package
updates. Presumably the root cause can be found elsewhere...

regards,
Alex

"Charles C. Berry"  writes:

> On Sun, 25 Dec 2016, joa...@verona.se wrote:
>
>> aaermo...@gmail.com writes:
>>
>>> Hi all!
>>>
>>> Recently I've experienced a kind of a problem - my literate Emacs config
>>> stopped tangling correctly, only a subset of code blocks were found in
>>> resulting .el file.
>>> I've looked at it a bit closer and it seems now (not earlier than 9.0.2)
>>> the :tangle clause became required. I've searched Org repo but failed to
>>> find a respective commit or any reference to the relevant info.
>>
>
> I don't think the problem lies with any revision to org.
>
> First, what `C-h v org-babel-default-header-args RET' shows below is
> unchanged for at least a year:
>
> --8<---cut here---start->8---
>
> org-babel-default-header-args is a variable defined in ‘ob-core.el’.
> Its value is ((:session . "none")
>   (:results . "replace")
>   (:exports . "code")
>   (:cache . "no")
>   (:noweb . "no")
>   (:hlines . "no")
>   (:tangle . "no"))
>
> ...
> --8<---cut here---end--->8---
>
> Note that `(:tangle . "no")' sets the default behavior.
>
> Second, I have files that depend on the above. i.e. I set the header
> on a few blocks to `:tangle yes' and leave the rest alone, relying on
> the above default to keep them from being tangled.
>
>
>> I also experienced the same behaviour. :tangle became required, which it
>> wasn't previously.
>>
>> My solution was just to add the ":tangle yes" tag everywhere.
>>
>>
>>>
>>> Can anyone point me to the right direction?
>>>
>
> Use
>
> #+PROPERTY: header-args :tangle yes
>
> (and type `C-c C-c' to reset the buffer the first time you type it)
>
> and review
>
> (info "(org) Using header arguments")
>
> for tips on how to control the application of header args.
>
> HTH,
>
> Chuck


signature.asc
Description: PGP signature

Re: [O] Literate config and :tangle clauses

[aaermolov]

Yes, I've ended up doing the same. It's not a problem at all, but I was
just curious how has it gone that way.

regards,
Alex

joa...@verona.se writes:

> aaermo...@gmail.com writes:
>
>> Hi all!
>>
>> Recently I've experienced a kind of a problem - my literate Emacs config
>> stopped tangling correctly, only a subset of code blocks were found in
>> resulting .el file. 
>> I've looked at it a bit closer and it seems now (not earlier than 9.0.2)
>> the :tangle clause became required. I've searched Org repo but failed to
>> find a respective commit or any reference to the relevant info.
>
> I also experienced the same behaviour. :tangle became required, which it
> wasn't previously.
>
> My solution was just to add the ":tangle yes" tag everywhere.
>
>
>>
>> Can anyone point me to the right direction? 
>>
>> regards,
>> Alex
>>
> -- 
> Joakim Verona


signature.asc
Description: PGP signature

[O] Literate config and :tangle clauses

[aaermolov]

Hi all!

Recently I've experienced a kind of a problem - my literate Emacs config
stopped tangling correctly, only a subset of code blocks were found in
resulting .el file. 
I've looked at it a bit closer and it seems now (not earlier than 9.0.2)
the :tangle clause became required. I've searched Org repo but failed to
find a respective commit or any reference to the relevant info.

Can anyone point me to the right direction? 

regards,
Alex


signature.asc
Description: PGP signature

Re: [O] Remove Org from Emacs repository?

[aaermolov]

2 cents from me...

Besides I continuously see many users praising Emacs just for Org
presence (they even may be completely non-technical users), I'm
personally think Org may be removed from Emacs distribution because:

1) all Reuben's argument seems sane;
2) there are situations when someone wants particular version of Org,
   and it may be not tne one bundled with Emacs. In this case someone
   should perform extra steps to ensure things are going the right way.
   When Org will be available only from ELPA, it will be SPOT for such cases.  

Reuben Thomas  writes:

> Now that Emacs has had package.el for some years, and Org is installable
> directly from GNU ELPA, would it be a good idea to remove Org from Emacs's
> source repository?
>
> The current situation is left over from before Emacs had package.el, and I
> see no compelling reason to keep it. Org is too big and distinct to be
> swallowed by Emacs; it doesn't make much sense to keep its current half-in,
> half-out state; so logically it seems sensible to take it out.
>
> I am asking this question from an Org point of view; I will ask the Emacs
> maintainers separately for their perspective.
>
> I think it would benefit Emacs too, as there would be less code to maintain
> (even though Org is quasi-external at present, it still has to build
> successfully as part of an Emacs build), and the Emacs distribution would
> be slimmer for non-Org users.
>
> Of course, Emacs "distributions" would still be able to include Org
> out-of-the box if they wished.
>
> -- 
> http://rrt.sc3d.org


signature.asc
Description: PGP signature

Re: [O] Exporting cyrillic documents to LaTeX/PDF

[aaermolov]

Thanks Rasmus, it works!

xelatex solves the problem.

In case someone interested, here is the solution (Gentoo distro):
Add "app-text/texlive l10n_ru"
somewhere portage/package.use info lives
it will trigger "dev-texlive/texlive-langcyrillic" package installation 
(or install it directly if you wish).

Alex

Rasmus  writes:

> aaermo...@gmail.com writes:
>
>> I have a problem exporting org-mode documents with cyrillic text to
>> LaTeX/PDF. As a result, Emacs says "PDF file produced with errors." and
>> only English text is displayed in resulting pdf, cyrillic chunks are
>> just omitted. 
>>
>> Googling this topic gave me a bunch of contradictory ways to proceed but
>> none of them give me a desired result. Searching maillist archives helps
>> no further.
>>
>> Could you please point me in more or less right direction, appropriate
>> keywords, etc?
>
> Did you try with xelatex?  Try adding:
>
> #+latex_compiler: xelatex
>
> Obviously, you must have a working xelatex system to begin with.  Lualatex
> should also work.
>
> Hope it helps,
> Rasmus
>
> -- 
> Enough with the blah blah!


signature.asc
Description: PGP signature

[O] Exporting cyrillic documents to LaTeX/PDF

[aaermolov]

Hi all,

I have a problem exporting org-mode documents with cyrillic text to
LaTeX/PDF. As a result, Emacs says "PDF file produced with errors." and
only English text is displayed in resulting pdf, cyrillic chunks are
just omitted. 

Googling this topic gave me a bunch of contradictory ways to proceed but
none of them give me a desired result. Searching maillist archives helps
no further.

Could you please point me in more or less right direction, appropriate
keywords, etc?


signature.asc
Description: PGP signature

Re: [O] Defining directory tree structure from org-attach to reflect headers

[aaermolov]

I'm not completely up to topic, but it seems to me that org-attach
machinery is more about a content-addressable storage, so it makes
little sense for what you want this way.

But those who know more, can obviously correct me.

cheers,
Alex

Rainer M Krug  writes:

> Hi
>
> I have effectively the same question as Adm here:
> [http://emacs.stackexchange.com/questions/26412/human-readable-directory-tree-with-org-attach]
>
> I would like to have the directory tree of the attachments managed by
> org-attach to reflect the document structure as defined by the
> headlines.
>
> To quote from his question:
>
> ,
> | * This headline
> |   ** This sub-headline 1
> |   ** This sub-headline 2
> | * This second headline
> | 
> | matches to the directory structure:
> | 
> | - This headline
> |   - This sub-headline 1
> |   - This sub-headline 2
> | - This second headline
> `
>
> I started using to set the directories, but for this I need the
> additional step of defining it per subtree. Is there a way to configure
> org-attach to automatically use the header name instead of the uuid?
>
> Thanks,
>
> Rainer
>
>
> -- 
> Rainer M. Krug
> email: Rainerkrugsde
> PGP: 0x0F52F982


signature.asc
Description: PGP signature