Re: Follow-up on: Quick fix: ATTR_BEAMER not showing in autocompletion

2024-11-04 Thread Ihor Radchenko
Pedro Andres Aranda Gutierrez writes: > right, but if they directly were buffer-local from the very beginning, one > wouldn't have to be jumping between files to understand that. > Call it 'pedantic time optimisation' from someone getting older ;-) Maybe. But there is no clear benefit to change

Re: Follow-up on: Quick fix: ATTR_BEAMER not showing in autocompletion

2024-11-03 Thread Pedro Andres Aranda Gutierrez
Hi, right, but if they directly were buffer-local from the very beginning, one wouldn't have to be jumping between files to understand that. Call it 'pedantic time optimisation' from someone getting older ;-) best, /PA On Sun, 3 Nov 2024 at 19:02, Ihor Radchenko wrote: > Pedro Andres Aranda Gut

Re: Follow-up on: Quick fix: ATTR_BEAMER not showing in autocompletion

2024-11-03 Thread Ihor Radchenko
Pedro Andres Aranda Gutierrez writes: > Observation: Variables controlled by #+STARTUP are ‘defcustom’, so > they will interfere: for example, the beamer startup option may appear > when working on the lecture file or may be suppressed in the > presentations depending on how I load the org-files.

Follow-up on: Quick fix: ATTR_BEAMER not showing in autocompletion

2024-10-06 Thread Pedro Andres Aranda Gutierrez
HI again, After quick fix, a couple of more detailed thoughts: Use case: I have my lecture notes, slides and laboratory manuals as org files. There are situations where I need to edit in parallel the notes and the slides. Observation: Variables controlled by #+STARTUP are ‘defcustom’, so they w