Re: [O] [DEV] Bump Emacs requirement to 24.4?

Hi, Two reasons to at least jump to 24.4: - nadvice.el: we can clean up all the advising in the code and advocate add-function. This is already employed in upstream Emacs. - prettify-symbols-mode: Perhaps some entity display code can be dropped in favor of

Re: [O] [DEV] Text quoting backports

Hello, Kyle Meyer writes: > There have been several commits made recently in the Emacs repo related > to quoting style in docstrings and messages. I've backported the > changes touching Org files and pushed to the branch maint-quotes. I put > them there instead of installing

[O] [DEV] Text quoting backports

Hello, There have been several commits made recently in the Emacs repo related to quoting style in docstrings and messages. I've backported the changes touching Org files and pushed to the branch maint-quotes. I put them there instead of installing them directly on maint to allow time for

Re: [O] [DEV] Text quoting backports

Kyle Meyer kyleam.com> writes: > > There have been several commits made recently in the Emacs repo related > to quoting style in docstrings and messages. I've backported the > changes touching Org files and pushed to the branch maint-quotes. I put > them there instead of installing them

Re: [O] [DEV] Text quoting backports

Rasmus writes: > Isn't this dependent on Emacs 25? Currently maint target emacs 23 and master > targets 24.3. They will only affect Emacs 25 users, but IIUC none of these would break the any supported Emacs versions. If the Emacs version doesn't have functions that look at

Re: [O] [DEV] Bump Emacs requirement to 24.4?

Hi Rasmus, Rasmus ras...@gmx.us writes: It would seem to me, that the natural conclusion from this is simply to EOL Org 8+ and move on to v9, no? (I'm not sure what you mean by EOL.) And surely I've not been clear (see my answer to Suvayu too): the whole purpose of this three-branches

Re: [O] [DEV] Bump Emacs requirement to 24.4?

Bastien writes: Here is my decision on this issue: - the Org 8.x series will be Emacs 23+ compatible. …and we should maybe do an 8.4 final release before it is frozen, but not drag it along furhter like you suggested in emacs-devel. - the Org 9.x series will be Emacs 24.3+ compatible.

Re: [O] [DEV] Bump Emacs requirement to 24.4?

Bastien b...@gnu.org writes: Hi Nicolas and all, As Achim said, we may have been miscommunicating, especially on whether it was about requiring Emacs 23+ or 24.3 vs 24.4. Here is my decision on this issue: - the Org 8.x series will be Emacs 23+ compatible. - the Org 9.x series will be

Re: [O] [DEV] Bump Emacs requirement to 24.4?

Hi Bastien, On Wed, Aug 19, 2015 at 11:40:09AM +0200, Bastien wrote: Suvayu Ali fatkasuvayu+li...@gmail.com writes: I'm slightly confused as-to why this special org-8-master branch is needed. As far as I understood from Achim's message (2nd paragraph):

Re: [O] [DEV] Bump Emacs requirement to 24.4?

Hi Bastien, On Wed, Aug 19, 2015 at 01:01:29AM +0200, Bastien wrote: The maint branch continues to be used to work on minor releases, as it has always been used. Instead of reverting changes from the master branch (you clearly don't want to do that, and I don't either), I suggest we

Re: [O] [DEV] Bump Emacs requirement to 24.4?

Hi Suvayu, Suvayu Ali fatkasuvayu+li...@gmail.com writes: I'm slightly confused as-to why this special org-8-master branch is needed. As far as I understood from Achim's message (2nd paragraph): http://mid.gmane.org/87twrzkbow.fsf@Rainer.invalid, that so far maint supports Emacs 23.

Re: [O] [DEV] Bump Emacs requirement to 24.4?

Hi David, David Engster d...@randomsample.de writes: Bastien writes: Emacs 23 and XEmacs support will be officially dropped as of Org 9.0. Support for XEmacs should be dropped right away; it would just state a fact, as Org didn't even compile with XEmacs for quite some time now (and nobody

Re: [O] [DEV] Bump Emacs requirement to 24.4?

Hi Nicolas and all, As Achim said, we may have been miscommunicating, especially on whether it was about requiring Emacs 23+ or 24.3 vs 24.4. Here is my decision on this issue: - the Org 8.x series will be Emacs 23+ compatible. - the Org 9.x series will be Emacs 24.3+ compatible. Emacs 23 and

Re: [O] [DEV] Bump Emacs requirement to 24.4?

Bastien writes: Emacs 23 and XEmacs support will be officially dropped as of Org 9.0. Support for XEmacs should be dropped right away; it would just state a fact, as Org didn't even compile with XEmacs for quite some time now (and nobody complained). I recognize having the manpower to watch

Re: [O] [DEV] Bump Emacs requirement to 24.4?

Hi Achim, Achim Gratz strom...@nexgo.de writes: Since it already has happened and the general consensus seems to be that we should go there eventually, just maybe not right now, I don't see why we suddenly also need to re-define what master is about. The redefinition already happened (i.e.

Re: [O] [DEV] Bump Emacs requirement to 24.4?

Bastien writes: So my suggestion still stands: - let's keep master in the current compatibility state since the question you asked still needs to be answer (it's just 10 days since it was asked). - let's use a dedicated branch for commits requiring Emacs 24.3+. I'm with Nicolas on this

Re: [O] [DEV] Bump Emacs requirement to 24.4?

Bastien Guerry writes: The redefinition already happened (i.e. the master branch is about Org+Emacs 24.3+) and it happened before we could reach a consensus about it, or simply take the time to really discuss it as we need. I'm trying to find the best conditions to move forward here. Well,

Re: [O] [DEV] Bump Emacs requirement to 24.4?

Hi Nicolas, Nicolas Goaziou m...@nicolasgoaziou.fr writes: No. You asked weather it was fine to require Emacs 24.4 in your original message, then people pointed out that Emacs 24.3 was still widely used, then you said it was fine to require Emacs 24.3, just Emacs 24.4 was icing on the cake.

Re: [O] [DEV] Bump Emacs requirement to 24.4?

Hi, There is no rush for this change. I will ask on the emacs-devel mailing list for advice on what seems best to support. Rasmus, can you revert the 24.3 requirement on org.el for now ? Let's not make changes in the master branch that push the decision when it is not taken yet. Thanks, --

Re: [O] [DEV] Bump Emacs requirement to 24.4?

Hello, Bastien Guerry b...@gnu.org writes: There is no rush for this change. I will ask on the emacs-devel mailing list for advice on what seems best to support. Rasmus, can you revert the 24.3 requirement on org.el for now ? Let's not make changes in the master branch that push the

Re: [O] [DEV] Bump Emacs requirement to 24.4?

Hello, Achim Gratz strom...@nexgo.de writes: Debian Squeeze LTS or whatever they call it doesn't w/o backports. RHEL6 doesn't have it w/o epel (RHEL7 has 24.3 IIRC). RaspberryPi doesn't have it. I don't think we have a lot of Org users on RaspberryPi. I'm still falling over Emacs 22 in

Re: [O] [DEV] Bump Emacs requirement to 24.4?

Hello, Bastien Guerry b...@gnu.org writes: Yes, we should have waited for the decision to be taken for this. AFAIU, the decision was between 24.3 and 24.4. It isn't clear to me that there was an hesitation about dropping Emacs 23 support. I don't know, but we have only little information on

Re: [O] [DEV] Bump Emacs requirement to 24.4?

Hi Nicolas, Nicolas Goaziou m...@nicolasgoaziou.fr writes: Master branch is already 24.3+ (with compilation warnings, 24.4+ without them): I committed org-lint.el, moved some libraries to lexical binding, etc. Yes, we should have waited for the decision to be taken for this. Is there any

Re: [O] [DEV] Bump Emacs requirement to 24.4?

Nicolas Goaziou writes: Just to be sure, can we require Emacs 24.4 for development version (a.k.a. Org 8.4)? As a data point, Debian stable provides it. Debian Squeeze LTS or whatever they call it doesn't w/o backports. RHEL6 doesn't have it w/o epel (RHEL7 has 24.3 IIRC). RaspberryPi doesn't

Re: [O] [DEV] Bump Emacs requirement to 24.4?

Bastien Guerry b...@gnu.org writes: Hi Nicolas, Nicolas Goaziou m...@nicolasgoaziou.fr writes: Master branch is already 24.3+ (with compilation warnings, 24.4+ without them): I committed org-lint.el, moved some libraries to lexical binding, etc. Yes, we should have waited for the

Re: [O] [DEV] Bump Emacs requirement to 24.4?

Rasmus ras...@gmx.us writes: But then what will master hold and what would be the point of it? It sounds like a way to rename master to branch9.0... The point is to allow committing changes that depend on this requirement without forcing the requirement on master. We can also simply revert

Re: [O] [DEV] Bump Emacs requirement to 24.4?

Bastien Guerry b...@gnu.org writes: We can also simply revert those change and wait for the decision to be taken. This is a matter of waiting ~10 days I'd say. Also, Emacs 24.3 was released in March, 2013. By the time the next Org is released, it will be more than 3 years old. Com'on :)

Re: [O] [DEV] Bump Emacs requirement to 24.4?

Bastien Guerry b...@gnu.org writes: We can also simply revert those change and wait for the decision to be taken. This is a matter of waiting ~10 days I'd say. Revert any commit you want to your heart's content. Note however, that I deleted my corresponding local branches, so you may want to

Re: [O] [DEV] Bump Emacs requirement to 24.4?

Hi Nicolas, Nicolas Goaziou m...@nicolasgoaziou.fr writes: AFAIU, the decision was between 24.3 and 24.4. No. You asked weather it was fine to require Emacs 24.4 in your original message, then people pointed out that Emacs 24.3 was still widely used, then you said it was fine to require Emacs

Re: [O] [DEV] Bump Emacs requirement to 24.4?

Bastien Guerry writes: My simple point is: let's get more information and let's take a proper decision. Let's not force the change. I took a look at what is presently supported by Red Hat, Ubuntu, and OpenSuSE in their long term support releases. The results: emacs 23.1 (RHEL 6.0, Ubuntu

Re: [O] [DEV] Bump Emacs requirement to 24.4?

Bastien Guerry b...@gnu.org writes: No. You asked weather it was fine to require Emacs 24.4 in your original message, then people pointed out that Emacs 24.3 was still widely used, then you said it was fine to require Emacs 24.3, just Emacs 24.4 was icing on the cake. That's correct,

Re: [O] [DEV] Bump Emacs requirement to 24.4?

Robert Klein rokl...@roklein.de writes: On Wed, 05 Aug 2015 23:51:32 +0200 Rasmus ras...@gmx.us wrote: Nicolas Goaziou m...@nicolasgoaziou.fr writes: Just to be sure, can we require Emacs 24.4 for development version (a.k.a. Org 8.4)? As a data point, Debian stable provides it. Are

Re: [O] [DEV] Bump Emacs requirement to 24.4?

On Thu, 06 Aug 2015 10:03:17 +0200 Nicolas Goaziou m...@nicolasgoaziou.fr wrote: Robert Klein rokl...@roklein.de writes: On Wed, 05 Aug 2015 23:51:32 +0200 Rasmus ras...@gmx.us wrote: Nicolas Goaziou m...@nicolasgoaziou.fr writes: Just to be sure, can we require Emacs 24.4 for

Re: [O] [DEV] Bump Emacs requirement to 24.4?

Nicolas Goaziou m...@nicolasgoaziou.fr writes: Bumping requirements to Emacs 24.3 instead of 24.4 is no biggie. 24.4 is just icing on the cake. I don't care about 24.{3,4,5}. In the end, on a very pragmatic level it's a question of which machines are shown on David's buildbot... Personally,

[O] [DEV] Bump Emacs requirement to 24.4?

Hello, Just to be sure, can we require Emacs 24.4 for development version (a.k.a. Org 8.4)? As a data point, Debian stable provides it. Also, what is the status of XEmacs support? AFAIU Org 8.3 doesn't build on XEmacs but no one is complaining. We may as well drop it and ignore most of

Re: [O] [DEV] Bump Emacs requirement to 24.4?

+1 On Wed, Aug 5, 2015 at 3:38 PM Nicolas Goaziou m...@nicolasgoaziou.fr wrote: Hello, Just to be sure, can we require Emacs 24.4 for development version (a.k.a. Org 8.4)? As a data point, Debian stable provides it. Also, what is the status of XEmacs support? AFAIU Org 8.3 doesn't build

Re: [O] [DEV] Bump Emacs requirement to 24.4?

On Wed, Aug 05, 2015 at 09:39:19PM +0200, Nicolas Goaziou wrote: Hello, Just to be sure, can we require Emacs 24.4 for development version (a.k.a. Org 8.4)? As a data point, Debian stable provides it. Also, what is the status of XEmacs support? AFAIU Org 8.3 doesn't build on XEmacs but no

Re: [O] [DEV] Bump Emacs requirement to 24.4?

Nicolas Goaziou m...@nicolasgoaziou.fr writes: Just to be sure, can we require Emacs 24.4 for development version (a.k.a. Org 8.4)? As a data point, Debian stable provides it. Are the any differences between 24.4 and 24.5 that we care about? wrt the distros I care about: - Arch and Fedora

Re: [O] [DEV] Bump Emacs requirement to 24.4?

Hi Nicolas, Nicolas Goaziou m...@nicolasgoaziou.fr writes: Just to be sure, can we require Emacs 24.4 for development version (a.k.a. Org 8.4)? As a data point, Debian stable provides it. Before discussion 24.4 vs say 24.3... why? What compatibility code is a burden today? Also, what is the

Re: [O] [DEV] Bump Emacs requirement to 24.4?

Bastien Guerry b...@gnu.org writes: Before discussion 24.4 vs say 24.3... why? What compatibility code is a burden today? 24.3 is the minimum required to drop `org-link-escape-browser', which is currently buggy. 24.4 fixes `split-string' and introduces many changes at the lisp level (variadic

Re: [O] [DEV] Bump Emacs requirement to 24.4?

On Wed, 05 Aug 2015 23:51:32 +0200 Rasmus ras...@gmx.us wrote: Nicolas Goaziou m...@nicolasgoaziou.fr writes: Just to be sure, can we require Emacs 24.4 for development version (a.k.a. Org 8.4)? As a data point, Debian stable provides it. Are the any differences between 24.4 and 24.5

Re: [O] [dev] New version of org-index.el --- a personal index for org and beyond

Hi Alan, I see the same error, when starting with a vanilla emacs; so these errors were easy to fix (version 3.0.1): http://orgmode.org/w/org-mode.git?p=org-mode.git;a=blob_plain;f=contrib/lisp/org-index.el;hb=HEAD Thanx for reporting ! best regards Marc On 12/09/2014 09:02 PM, Alan

Re: [O] [dev] New version of org-index.el --- a personal index for org and beyond

On 2014-12-10 22:26, Marc Ihm m...@ihm.name writes: Hi Alan, I see the same error, when starting with a vanilla emacs; so these errors were easy to fix (version 3.0.1): http://orgmode.org/w/org-mode.git?p=org-mode.git;a=blob_plain;f=contrib/lisp/org-index.el;hb=HEAD It works great now,

Re: [O] [dev] New version of org-index.el --- a personal index for org and beyond

Hello, On 2014-12-08 22:00, Marc Ihm m...@ihm.name writes: Hi all, the new version 3.0.0 of org-index.el has been uploaded to the contrib-directory of orgs git-repository. Features include improved setup-assistant and the new command add, which adds the current node to your index.

Re: [O] [dev] New version of org-index.el --- a personal index for org and beyond

On 2014-12-09 19:58, Alan Schmitt alan.schm...@polytechnique.org writes: I've given it a try, and upon creation there is a backtrace (when I'm done with the setup): Debugger entered--Lisp error: (wrong-type-argument integer-or-marker-p nil) org-index--goto-list(columns-and-flags)

[O] [dev] New version of org-index.el --- a personal index for org and beyond

Hi all, the new version 3.0.0 of org-index.el has been uploaded to the contrib-directory of orgs git-repository. Features include improved setup-assistant and the new command add, which adds the current node to your index. Moreover the structure of the index-table and its flags has been

Re: [O] [dev] New version of org-index.el --- A personal index for org and beyond

m...@ihm.name writes: Here are a few notes I'm taking as I'm playing with it. First, the table seems to be different from the one on worg. Here are the columns I have: | | | | | | comment | | ref | link | created | count;s |

Re: [O] [dev] New version of org-index.el --- A personal index for org and beyond

Hello Marc, m...@ihm.name writes: Hello, please find attached version 2.3 of org-index.el. See also http://orgmode.org/worg/code/elisp/org-index.el and the contrib-directory of org. The most notable feature of this version is an assistant which provides easy setup. I'm trying org-index,

Re: [O] [dev] New version of org-index.el --- A personal index for org and beyond

Hi Alan Alan Schmitt alan.schm...@polytechnique.org writes: I'm trying org-index, and I let the assistant build the table for me. At the end of the set, this error occurred: , | Saved org-index-id '50E94CE9-06B3-452E-96B6-FA47AA08B9D6' to /Users/schmitta/.emacs.d/custom.el | let:

Re: [O] [dev] New version of org-index.el --- A personal index for org and beyond

On Thu, Aug 01, 2013 at 10:17:42PM +0200, Marc Ihm wrote: Hello, please find attached version 2.3 of org-index.el. See also http://orgmode.org/worg/code/elisp/org-index.el and the contrib-directory of org. The most notable feature of this version is an assistant which provides easy

Re: [O] [dev] New version of org-favtable.el -- Lookup table of favorite references and links

Hi, org-favtable now has its own documentation at worg: http://orgmode.org/worg/org-contrib/org-favtable.html Its table of contents reads like this: * Introduction and Overview * Three scenarios of typical usage * Some concepts of org-favtable * Installation and setup * A working

Re: [O] [dev] New version of org-favtable.el -- Lookup table of favorite references and links

Hi Marc-Oliver, Marc-Oliver Ihm m...@ihm.name writes: find a new version of org-favtable.el attached and on worg. if you want to have org-favtable.el in contrib/lisp/ please let me know. It'd be nice to have a Worg page describing what it does exactly: extracting some of the comments you have

Re: [O] [DEV] New version of org-reftable.el

Hi Marc-Oliver, Marc-Oliver Ihm m...@ihm.name writes: Version 2.0 of org-reftable.el has arrived at worg. Please find it as: http://orgmode.org/worg/code/elisp/org-reftable.el I've not had time to test the package but I hope others will do. If you/they think this can be a good

Re: [O] [DEV] New version of org-reftable.el

Hi Bastien, Hi all ! Currently I often use this package to quickly navigate within my org-files. Entering a keyword gives me a list of nodes associated with this keyword; within this list, often used entries appear at the top, so that the desired entry can be spotted very fast. This will be

[O] [DEV] New version of org-reftable.el

Hello all ! Version 2.0 of org-reftable.el has arrived at worg. Please find it as: http://orgmode.org/worg/code/elisp/org-reftable.el Citing from its documentation: ;;; org-reftable.el --- Ordered lookup table for reference numbers ;; ;; Purpose: ;; ;; Create, search and look up numbers

[O] [dev] Org inline src block not being triggered in org-export.el

I'm testing inline source and nothing is being printed. Nothing is happening. No errors, no messages, no nothing. Definition to the corret inline-src-block function is in the definition list. But it does not seems that is executing at all. So, what am I doing wrong? :) -- org mode source -- *

Re: [O] [dev] Org inline src block not being triggered in org-export.el

Luis Anaya papoan...@hotmail.com writes: I'm testing inline source and nothing is being printed. Nothing is happening. No errors, no messages, no nothing. Definition to the corret inline-src-block function is in the definition list. But it does not seems that is executing at all. So, what

Re: [O] [dev] About a beamer back-end

Hi Nicolas, As I announced in another thread, I'm starting a Beamer back-end for the new export engine. Though, before I start hacking, I have a question about environments. Will this new backend support presentations in subtrees? I think, what I want is not possible with the current one.

Re: [O] [dev] About a beamer back-end

Hi Andreas, On Thu, Jun 28, 2012 at 12:40 PM, Andreas Leha andreas.l...@med.uni-goettingen.de wrote: Will this new backend support presentations in subtrees?  I think, what I want is not possible with the current one. As an example, consider files structured like this: #+begin_src org *

Re: [O] [dev] About a beamer back-end

Hi suvayu ali, Hi Andreas, On Thu, Jun 28, 2012 at 12:40 PM, Andreas Leha andreas.l...@med.uni-goettingen.de wrote: Will this new backend support presentations in subtrees?  I think, what I want is not possible with the current one. As an example, consider files structured like this:

Re: [O] [dev] About a beamer back-end

Nicolas, I'll keep headlines for blocks. But I think I'll introduce a couple of small changes. I really like all the changes you propose. The result would appear to be a clean design. I particularly like the defaulting of headlines to blocks. Unlike others, I am not bothered about *alert*

Re: [O] [dev] About a beamer back-end

Hello, Eric S Fraga e.fr...@ucl.ac.uk writes: See `org-element-drag-backward' and `org-element-drag-forward'. Okay. Will it be easy to bind these to M-up etc. to achieve consistent behaviour? I.e. does org-metaup know what to do with blocks? I hope that, one day, they will replace

Re: [O] [dev] About a beamer back-end

Nicolas Goaziou n.goaz...@gmail.com writes: - There is no separate syntax for \alert{} command: it is the default output for bold objects (i.e. *text* becomes \alert{text}). Would bold then be archived with some other markup? Or would it just not be possible to get bold text (without

Re: [O] [dev] About a beamer back-end

Hi Nicolas, First, a big thank you for your work on this as well... Here, inline, a couple of quick remarks... Nicolas Goaziou wrote: Eric S Fraga e.fr...@ucl.ac.uk writes: See `org-element-drag-backward' and `org-element-drag-forward'. Okay. Will it be easy to bind these to M-up etc. to

Re: [O] [dev] About a beamer back-end

Hello, Rasmus ras...@gmx.us writes: - There is no separate syntax for \alert{} command: it is the default output for bold objects (i.e. *text* becomes \alert{text}). Would bold then be archived with some other markup? Or would it just not be possible to get bold text (without defaulting

Re: [O] [dev] About a beamer back-end

Nicolas Goaziou n.goaz...@gmail.com writes: The noframe tag sounds good. Do you have any example of the use you have in mind? I don't know what kind of contents one would like add between frames (excepted notes). - If you are to repeat frames - Imagine a complicated tikz picture which

Re: [O] [dev] About a beamer back-end

Hi Nicolas, On Thu, Jun 21, 2012 at 4:37 PM, Nicolas Goaziou n.goaz...@gmail.com wrote: If you want to try them out (there has been no serious debugging for them), you can  (defalias 'org-metaup 'org-element-drag-backward) `org-element-drag-backward' is a strict super-set for `org-metaup'.

Re: [O] [dev] About a beamer back-end

Hello, Sebastien Vauban wxhgmqzgwmuf-genee64ty+gs+fvcfc7...@public.gmane.org writes: - Sectioning and packages are extracted from `org-e-latex-classes'. Since calling Beamer back-end is explicit, it can be applied on any tex file, not only when that file starts with

Re: [O] [dev] About a beamer back-end

I also quite like using headlines for blocks, for many of the same reasons Eric mentioned. In addition, I regularly use column view to set BEAMER_env, BEAMER_envargs, BEAMER_extra, etc., and column view operates on headlines. Greg On Jun 20, 2012, at 5:04 AM, Eric S Fraga wrote: Nicolas

Re: [O] [dev] About a beamer back-end

Hi all, Greg Tucker-Kellogg wrote: On Jun 20, 2012, at 5:04 AM, Eric S Fraga wrote: Nicolas Goaziou n.goaz...@gmail.com writes: Eric S Fraga e.fr...@ucl.ac.uk writes: Well, I will have to chime in with a contrary view. I like using headlines to define blocks, and I use blocks on almost

Re: [O] [dev] About a beamer back-end

Sebastien Vauban wxhgmqzgw...@spammotel.com writes: [...] Personally, I dislike using headlines for *anything* that's in the frame. I like the idea that headlines do show the structure of your presentation: - (optionally) sections and subsections for the sidebar - frame title (and subtitle)

Re: [O] [dev] About a beamer back-end

Hello, Eric S Fraga e.fr...@ucl.ac.uk writes: Well, I will have to chime in with a contrary view. I like using headlines to define blocks, and I use blocks on almost every frame. I have the following reasons for preferring a headline approach: - the proposed approach does not easily (at

Re: [O] [dev] About a beamer back-end

Hi Nicolas, first of all, I think the block idea is a good one, as long a notes will remain headlines. Nevertheless I often had the problem in my documents, that I wanted to insert code between frames. It would be great, if you could provide a clean solution for such things, too.

Re: [O] [dev] About a beamer back-end

Avdi Grimm gro...@inbox.avdi.org writes: On Fri, Jun 15, 2012 at 12:41 PM, suvayu ali fatkasuvayu+li...@gmail.com wrote: With this syntax it would be very easy to write both really long (40-50 frames) as well as quick and short presentations. I've only been using Org and Beamer for a

Re: [O] [dev] About a beamer back-end

Nicolas Goaziou n.goaz...@gmail.com writes: As I announced in another thread, I'm starting a Beamer back-end for the new export engine. This is indeed good news. Here are some concerns that I would like to address compared to the current exporter. - Operating with pauses are overly hard.

Re: [O] [dev] About a beamer back-end

Hello Rasmus, Rasmus wrote: - Operating with pauses are overly hard. One can specify overlays in properties, but n is just not very convenient, as I may have to introduce a new number jn. I prefer the pause, but it does not feel 'natural' in the current org-beamer (IMO). I

Re: [O] [dev] About a beamer back-end

Sebastien Vauban IIUC, you seem to say it's difficult to use the overlay notation, but you can use it very easily that way: ** Overlay effects \\ Keep the suspense! *** Time bomb:B_block: :PROPERTIES: :BEAMER_env: block

Re: [O] [dev] About a beamer back-end

Hi Eric, On Mon, Jun 18, 2012 at 9:50 AM, Eric S Fraga e.fr...@ucl.ac.uk wrote: Avdi Grimm gro...@inbox.avdi.org writes: On Fri, Jun 15, 2012 at 12:41 PM, suvayu ali fatkasuvayu+li...@gmail.com  wrote: With this syntax it would be very easy to write both really long (40-50 frames) as well

[O] [dev] About a beamer back-end

Hello, As I announced in another thread, I'm starting a Beamer back-end for the new export engine. Though, before I start hacking, I have a question about environments. I'm wondering if it is really interesting to have every environment set up from headlines. I understand it allows to use

Re: [O] [dev] About a beamer back-end

Hi Nicolas, First a big thank you for all your efforts over the last year. On Fri, Jun 15, 2012 at 5:08 PM, Nicolas Goaziou n.goaz...@gmail.com wrote: I'm wondering if it is really interesting to have every environment set up from headlines. I understand it allows to use column view but, from

Re: [O] [dev] About a beamer back-end

On Fri, Jun 15, 2012 at 12:41 PM, suvayu ali fatkasuvayu+li...@gmail.com wrote: With this syntax it would be very easy to write both really long (40-50 frames) as well as quick and short presentations. I've only been using Org and Beamer for a little while, but if I understand it correctly

Re: [O] [DEV] New git workflow

Hi Nick, I did not mean to imply git is not capable of working that way. It's more a question of what is accepted practice and most importantly, what fits the problem you actually have. The difference between both approaches, it seems to me, shows when there is a difference between the fix

Re: [O] [DEV] New git workflow

Simon Thum simon.t...@gmx.de writes: Hi all, Hello, [...] Many projects use the IMO more sane model of release branches (or maintenance branches, if you prefer) for major releases. Minor ones are tagged on those branches, and back-porting critical fixes is much cleaner: Fixes and

Re: [O] [DEV] New git workflow

Hi Daniel, On 03/24/2012 12:05 PM, Daniel Dehennin wrote: Simon Thumsimon.t...@gmx.de writes: It seems that one problem with cherry-picking is the tracking of what is in which branch and from where it comes. I'm not a git neither DVCS guru, but daggyfixes[1][2][3] is saner than

Re: [O] [DEV] New git workflow

Simon Thum simon.t...@gmx.de wrote: Hi Daniel, On 03/24/2012 12:05 PM, Daniel Dehennin wrote: Simon Thumsimon.t...@gmx.de writes: It seems that one problem with cherry-picking is the tracking of what is in which branch and from where it comes. I'm not a git neither DVCS guru, but

Re: [O] [DEV] New git workflow

Hi Achim, On 03/20/2012 11:27 PM, Achim Gratz wrote: Sorry, but cherry-picking into multiple release branches would simply not be a sane development model for a small project like orgmode. I just wanted to make sure it's considered. Whether multiple branches are involved depends mainly on

Re: [O] [DEV] New git workflow

Simon Thum simon.t...@gmx.de writes: Whether multiple branches are involved depends mainly on what releases one intends to maintain. The nice thing in the model is the gradual maintenance: A really critical fix could see more backports than a nicety. Yes. Bastien has to make that decision

Re: [O] [DEV] New git workflow

Hi Achim and Bastien, in case you fancy with the release-branch model now or in the foreseeable future, I'll probably be able to take over some of the work load in case it's a deciding factor. I've done that locally when necessary, and can claim enough git-foo. Cheers, Simon On 03/21/2012

Re: [O] [DEV] New git workflow

Bastien b...@altern.org writes: The main problem I see With this workflow is that releases are made from two different branches: bugfix releases are made from maint and major releases are made from master. This doesn't look right to me. That ain't necessarily so. IMHO, the release always has

Re: [O] [DEV] New git workflow

Achim Gratz strom...@nexgo.de writes: You would have to push this branch out to the public repo, otherwise the other people with access to the repo can't use it. I see you already did, had to reconfigure my refspecs for it to show up. Regards, Achim. -- +[Q+ Matrix-12 WAVE#46+305 Neuron

Re: [O] [DEV] New git workflow

Hi Achim, Achim Gratz strom...@nexgo.de writes: Bastien b...@altern.org writes: The main problem I see With this workflow is that releases are made from two different branches: bugfix releases are made from maint and major releases are made from master. This doesn't look right to me. That

Re: [O] [DEV] New git workflow

Let me summarise why I propose this new workflow: 1. Users will have a way to track *only releases* from git. 2. We will be able to use git hooks in order to automate the release process on the server. 3. The workflow looks clearer to me (may be 100% subjective.) The cost of the new setup

Re: [O] [DEV] New git workflow

Bastien b...@gnu.org writes: Agreed. What I want on top of this is a to have a branch where *every* commit corresponds to a single release. Fair enough: a three-branch model with a release branch at the side of bugfixing and bleeding edge. No. All hotfix branches should merge into master

Re: [O] [DEV] New git workflow

Hi all, as discussion started anyway, I'd like to mention that I see some problem with maint, that is, it only ever pertains to the latest release. It's hard to hotfix and release old versions in the proposed model. Moreover, maint is bound quite tightly to master. maint seems like a

Re: [O] [DEV] New git workflow

Simon Thum simon.t...@gmx.de writes: as discussion started anyway, I'd like to mention that I see some problem with maint, that is, it only ever pertains to the latest release. It's hard to hotfix and release old versions in the proposed model. IMHO, that was never the objective. Moreover,

Re: [O] [DEV] New git workflow

Hi Achim, Achim Gratz strom...@nexgo.de writes: Fair enough: a three-branch model with a release branch at the side of bugfixing and bleeding edge. This is directly inspired from this: http://nvie.com/posts/a-successful-git-branching-model/ with some simplifications. No. All hotfix

Re: [O] [DEV] New git workflow

Bastien b...@altern.org writes: version, their lifespan is not much (expect now, while we are ^^ except -- Bastien

[O] [DEV] New git workflow

Hi all, our current git workflow is pretty well summarised by Achim -- we have two main branches, master and maint, and we (try to) follow these rules: If it's a bugfix for something broken in a release version, commit to maint and merge maint back into master. If implementing a new

Re: [O] [dev] Implement ref link types

On the Org side, when a link like [[something]] or [[something][text]] is encountered in a buffer, the search would go on like this: 1. Search any something or #+target: something[1]. 1. A link to an invisible target will be replaced with _nothing_ (that's the point of being

Re: [O] [dev] Implement ref link types

Hello, Here is a new version of the patch built on top of master, along with test cases. If there is no objection, I'll push it to master in a couple of days. I really think that's a great feature to have in Org. Regards, -- Nicolas Goaziou From 2fdde87bb7f1241f3d24dbd8ae030a300fe8f0fc Mon

  1   2   >