emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Carsten Dominik <carsten.dominik@gmail.com>
To: Robin Green <greenrd@greenrd.org>
Cc: emacs-orgmode@gnu.org
Subject: Re: Bug: Column mode breaks beamer export [6.33trans]
Date: Wed, 16 Dec 2009 11:12:38 +0100	[thread overview]
Message-ID: <265D3B0A-345B-43D3-A251-CC11CD5188CC@gmail.com> (raw)
In-Reply-To: <m3skbcmzhe.wl%greenrd@greenrd.org>

Fixed, thank you for the report.

- Carsten

On Dec 15, 2009, at 9:07 AM, Robin Green wrote:

>
> After I enable "column view of properties" in the attached file,  
> export
> to PDF via LaTeX fails with the following error in the minibuffer:
>
> org-export-as-latex: Text is read-only: "Type `e' to edit property"
>
> Emacs  : GNU Emacs 23.1.50.1 (i486-pc-linux-gnu, GTK+ Version 2.18.0)
> of 2009-09-27 on palmer, modified by Debian
> Package: Org-mode version 6.33trans
>
> current state:
> ==============
> (setq
> org-export-latex-after-initial-vars-hook '(org-beamer-after-initial- 
> vars)
> org-agenda-files '("/src/greenrd/org")
> org-blocker-hook '(org-block-todo-from-checkboxes org-block-todo- 
> from-children-or-siblings-or-parent)
> org-checklist-export-function 'org-export-as-ascii
> org-after-todo-state-change-hook '(org-clock-out-if-current org- 
> checklist)
> org-agenda-todo-ignore-scheduled t
> org-startup-folded nil
> org-agenda-sorting-strategy '((agenda time-up priority-down effort- 
> up category-keep)
> 			       (todo priority-down effort-up category-keep)
> 			       (tags priority-down effort-up category-keep) (search  
> category-keep))
> org-agenda-prefix-format '((agenda . "  %-12:c%-12:T%?-12t% s")  
> (timeline . "  % s") (todo . "  %-12:c")
> 			    (tags . "  %-12:c") (search . "  %-12:c"))
> org-deadline-warning-days 900
> org-export-latex-format-toc-function 'org-export-latex-format-toc- 
> default
> org-agenda-skip-scheduled-if-done t
> org-export-preprocess-hook '(org-export-blocks-preprocess)
> org-tab-first-hook '(org-hide-block-toggle-maybe)
> org-src-mode-hook '(org-src-mode-configure-edit-buffer)
> org-confirm-shell-link-function 'yes-or-no-p
> org-export-first-hook '(org-beamer-initialize-open-trackers)
> org-todo-keywords '((sequence "TODO(t)" "QUESTION(q)" "PLANNING(p)"  
> "PENDING(e)" "STARTED(s)" "FINISHING(f)" "|"
> 		      "DONE(d)" "OBSOLETE(o)")
> 		     )
> org-agenda-before-write-hook '(org-agenda-add-entry-text)
> org-default-notes-file "/src/greenrd/org/remember.org"
> org-cycle-hook '(org-cycle-hide-archived-subtrees org-cycle-hide- 
> drawers org-cycle-show-empty-lines
> 		  org-optimize-window-after-visibility-change)
> org-mode-hook '(#[nil "\300\301\302\303\304$\207"
> 		   [org-add-hook change-major-mode-hook org-show-block-all append  
> local] 5]
> 		 )
> org-global-properties '(("Effort_ALL" . "0 0:10 0:30 1:00 2:00 3:00  
> 4:00 5:00 6:00 7:00 8:00"))
> org-return-follows-link t
> org-confirm-elisp-link-function 'yes-or-no-p
> org-beamer-environments-extra '(("figure" "F" "\\begin{figure}" "\ 
> \end{figure}"))
> org-agenda-todo-ignore-with-date t
> org-enforce-todo-dependencies t
> org-occur-hook '(org-first-headline-recenter)
> org-priority-start-cycle-with-default nil
> org-export-preprocess-before-selecting-backend-code-hook '(org- 
> beamer-select-beamer-code)
> org-agenda-todo-ignore-deadlines t
> org-modules '(org-bbdb org-bibtex org-gnus org-info org-jsinfo org- 
> irc org-mew org-mhe org-rmail org-vm org-wl
> 	       org-w3m org-checklist org-interactive-query org-man org- 
> registry)
> org-remember-templates '(("Web link" 119 "* %u %c \n\n%:region\n"  
> nil "Web links" nil))
> org-export-latex-final-hook '(org-beamer-amend-header org-beamer-fix- 
> toc org-beamer-auto-fragile-frames
> 			       org-beamer-place-default-actions-for-lists)
> org-enforce-todo-checkbox-dependencies t
> org-lowest-priority 70
> )
>
> #+STARTUP: beamer
> #+TITLE: Cohere: Towards Web 2.0 Argumentation
> #+AUTHOR: Simon Buckingham Shum
> #+LaTeX_CLASS: beamer
> #+LaTeX_CLASS_OPTIONS: [presentation]
> #+BEAMER_FRAME_LEVEL: 2
>
> #+BEAMER_HEADER_EXTRA: \usetheme{Szeged}\usecolortheme{wolverine} 
> \institute{Knowledge Media Institute, The Open University, UK}
> #+COLUMNS: %45ITEM %10BEAMER_env(Env) %10BEAMER_envargs(Env Args)  
> %4BEAMER_col(Col) %8BEAMER_extra(Extra)
> #+PROPERTY: BEAMER_col_ALL 0.1 0.2 0.3 0.4 0.5 0.6 0.7 0.8 0.9  
> 1.0 :ETC
>
> * Context
>
> ** What is argumentation software?
>
> *** *mapping* an argument					      :BMCOL:
> :PROPERTIES:
> :BEAMER_col: 0.5
> :BEAMER_envargs: C[T]
> :END:
>
> **** exposing its structure
>
> ***** typically in graph form
>
> *** for the purposes of this talk
> # I was going to say "typically" here, but I've only read 4-5 papers
> # in this area, so I can't be sure that it's typical. But that's how
> # it seems to me.
>
> **** *manual* data entry
>
> ***** not extraction
>
> **** can relate back to sources
>
> ***** links
>
> ***** video timestamps
>
> *** 							     :B_figure:BMCOL: :BMCOL:B_figure:
>    :PROPERTIES:
>    :BEAMER_col: 0.5
>    :BEAMER_env: figure
>    :END:
> \includegraphics[width=.7\columnwidth]{What_the_Bible_says.jpg}
>
> *** optionally
>
> **** *queries* for sub-arguments
>
> **** *multiple* I/O styles
>
> ***** directed graph
>
> ***** textual outline
>
> **** *collaborative editing*
>
> ** Why use argumentation software?
>
> *** example: climate change debates
>
> *** large and complex
>
> *** interdisciplinary
>
> **** science
>
> **** politics
>
> **** economics
>
> **** ethics
>
> *** timely
>
> **** Copenhagen conference
>
> ***** G77 delegates walk out
>
> *** relevant to Cohere
>
> **** ESSENCE project
>
> ** How might argumentation software help?
>
> *** could make large, complex arguments
>
> **** easier to navigate?
>
> **** easier to search?
>
> **** quicker to grasp?
>
> ***** or maybe /think/ you've grasped!
>
> **** less repetitive
>
> ***** but Flat Earthers still exist
>
> *** propagate updates in knowledge faster?
>
> **** propagate lies and stupid ideas faster?
>
> *** make debate more meritocratic?
>
> **** "blogging will level the playing field" all over again?
>
> ** What does this sound like?
>
> *** Wikipedia
>
> **** similar advantages have been attributed to it
>
> *** Is argumentation software reinventing the wheel?
>
> **** inaccessibility of WP technical & scientific articles
>
> **** different goals and value systems
>
> ***** WP: "Neutral Point of View" allows "he said / she said"
>
> ***** WP: Reliable Sources and Notability
>
> ***** WP: info not systematically structured along debate lines
>
> * The paper
>
> ** Introduction
>
> *** Motivation
>
> **** 								:B_quotation:
>     :PROPERTIES:
>     :BEAMER_env: quotation
>     :END:
> The context in which we find ourselves presents problems on a global  
> scale which will
> require negotiation and collaboration across national, cultural and  
> intellectual
> boundaries.
>
> *** Differences from related work
>
> **** distributed vs team-based
>
> **** asynchronous vs real-time
>
> **** introducing Web 2.0 principles
>
> ** Web 2.0 according to Buckingham Shum
>
> *** Some have dismissed as marketing term
>
> *** Four relevant elements
>
> **** Simple but engaging multimedia UIs
>
> ***** Web UIs should stand on a par with desktop UIs
>
> **** Emergent, not predefined, structure and semantics
>
> ***** let users define their own classification schemes
>
> ***** lightweight approaches (tags for blogs, social tagging) have  
> good uptake
>
> **** Social networks
>
> ***** status updates, friend recommendations, "reputation" indices
>
> **** Data interop, mashups and embedding
>
> ** Cohere data model
>
> *** 								   :B_figure:
>    :PROPERTIES:
>    :BEAMER_env: figure
>    :END:
> \includegraphics[width=.7\textwidth]{Cohere-data-model.png}
>
> ** Web 2.0-ish features
>
> *** Emergent structure
>
> **** Users can add own relation types
>
> ***** but seed data & autocompletion used to "nudge" users
>
> *** Social
>
> **** each idea links back to creating user
>
> **** Future / in development
>
> ***** sitewide feeds (like Twitter's "everyone")
>
> ***** active user stats
>
> ***** notification when your idea is connected to someone else's
>
> ***** notification when your idea is embedded in another website
>
> ***** different views for when multiple people work on one idea  
> (vague)
>
> ** Interop
>
> *** XML-based feeds (RSS/Atom)
>
> *** high level of addressability
>
> **** almost everything has a unique URL
>
> ***** allows embedding using HTML iframes
>
> *** import from Compendium offline argumentation tool
>
> *** Future
>
> **** export in a "variety of formats"
> _______________________________________________
> Emacs-orgmode mailing list
> Please use `Reply All' to send replies to the list.
> Emacs-orgmode@gnu.org
> http://lists.gnu.org/mailman/listinfo/emacs-orgmode

- Carsten

      reply	other threads:[~2009-12-16 10:47 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-15  8:07 Bug: Column mode breaks beamer export [6.33trans] Robin Green
2009-12-16 10:12 ` Carsten Dominik [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.orgmode.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=265D3B0A-345B-43D3-A251-CC11CD5188CC@gmail.com \
    --to=carsten.dominik@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=greenrd@greenrd.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).