emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Johnny <yggdrasil@gmx.co.uk>
To: Michael Brand <michael.ch.brand@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Org table with long lines visibility
Date: Mon, 09 May 2011 19:34:52 +0100	[thread overview]
Message-ID: <87bozblo37.fsf@gmx.co.uk> (raw)
In-Reply-To: <BANLkTinidaHN8EBRvVkRSOffPR_KrvcFXw@mail.gmail.com> (Michael Brand's message of "Mon, 9 May 2011 07:10:29 +0200")

Michael Brand <michael.ch.brand@gmail.com> writes:
> As I understand, the issue tracker on Worg
> http://orgmode.org/worg/org-issues.html
> is thought also as a wish-list and you may add this with the keyword
> WISH there. But I wouldn't expect too much from doing only this. The
> best in many cases is to try to implement by oneself and ask for help
> here where necessary. And it's fun too. To start to understand I would
> single step with Edebug firstly "TAB" in a table, then "C-c `" with
> "C-c C-q" and maybe also "S-<right>" on a reference after "C-c '" on
> #+TBLFM.
Thanks for the pointers. I will keep this on my todo-list, but starting
from minimal experience with lisp and none in debugging in emacs, I
wouldn't hold my breath. At least, now I know where to start though,
which is quite a step in the right direction.


  reply	other threads:[~2011-05-09 18:34 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-04 17:48 Org table with long lines visibility Johnny
2011-05-04 18:07 ` Juan Pechiar
2011-05-04 20:45   ` Johnny
2011-05-05  5:53     ` Michael Brand
2011-05-05  6:57 ` Michael Brand
2011-05-07 11:50   ` Johnny
2011-05-09  5:10     ` Michael Brand
2011-05-09 18:34       ` Johnny [this message]
2011-05-09 20:54         ` Michael Brand
2011-05-11  8:29 ` Carsten Dominik
2011-05-11  9:16   ` Michael Brand
2011-05-12  7:07   ` Eric S Fraga
2011-05-14 15:14   ` Johnny
2011-05-26  6:40     ` Carsten Dominik

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:

  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=87bozblo37.fsf@gmx.co.uk \
    --to=yggdrasil@gmx.co.uk \
    --cc=emacs-orgmode@gnu.org \
    --cc=michael.ch.brand@gmail.com \


* 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


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).