emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
* Is there a prominent place to announce user-interface changes ?
@ 2009-11-06 16:25 Torsten Wagner
  2009-11-07  6:40 ` Carsten Dominik
  0 siblings, 1 reply; 2+ messages in thread
From: Torsten Wagner @ 2009-11-06 16:25 UTC (permalink / raw)
  To: emacs-orgmode


[-- Attachment #1.1: Type: text/plain, Size: 1723 bytes --]

Hi everyone,

I'm not long on this list so don't kick me if I'm riding a dead horse. I
noticed the extreme speed of the development of org-mode (which is with no
doubts great). Sometimes, long time existing key-bindings have to be
rearranged (at least I noticed twice on the list) to make more space for the
steadily growing org-mode functionality. Always this create a lot of
discussion since many people familiar with the old bindings already even if
the seems to be sub-optimal now.

I just wonder, would it make sense to add a chapter 0 to the org-mode manual
and/or a dedicated page at a prominent place on worg which depicts only
those key-binding changes from release version to release version.
I just think about the changes which affect peoples daily work directly
maybe without warnings. That means from a standard changelog, exclude new
features, nothing about internal changes, no bugfix reports etc.. By this
way this list should be rather small but very important for (long-time)
org-mode users.
It is not enjoyable to find out in the middle of a "I just like to finish it
and come to the meeting in a second .... " time-frame that things change
during the last update. Emacs and org-mode make use of  8 fingers and 2
thumbs without much visual feedback. Therefore, most user use key-bindings
in a heart-beating, breathing way without thinking about it. Might be a good
idea if there is a central place to tell them to fight mentally for a while
against there subconscious or reconfigure it as they like.

Just an idea.

Regards

Torsten

BTW. I noticed that "[Orgmode]" is not added automatically to the subject.
Is this a feature or a bug :) ? I know from other mail-lists that this is
done automatically.

[-- Attachment #1.2: Type: text/html, Size: 2228 bytes --]

[-- Attachment #2: Type: text/plain, Size: 204 bytes --]

_______________________________________________
Emacs-orgmode mailing list
Remember: use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode

^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: Is there a prominent place to announce user-interface changes ?
  2009-11-06 16:25 Is there a prominent place to announce user-interface changes ? Torsten Wagner
@ 2009-11-07  6:40 ` Carsten Dominik
  0 siblings, 0 replies; 2+ messages in thread
From: Carsten Dominik @ 2009-11-07  6:40 UTC (permalink / raw)
  To: Torsten Wagner; +Cc: emacs-orgmode

Hi Torsten,

I do not think that such a chapter belongs into the manual.

The way I am doing this is writing release notes at

    http://orgmode.org/Changes.php

Whenever a change occurs that is of the character you describe, the
release notes contain "Inconsistent changes" as the first section and
highlight this change.

As for changes in the git repo between the releases, the only way to
protect yourself here is to read the mailing list, or the git logs
after pulling.

HTH

- Carsten

On Nov 6, 2009, at 5:25 PM, Torsten Wagner wrote:

> Hi everyone,
>
> I'm not long on this list so don't kick me if I'm riding a dead  
> horse. I noticed the extreme speed of the development of org-mode  
> (which is with no doubts great). Sometimes, long time existing key- 
> bindings have to be rearranged (at least I noticed twice on the  
> list) to make more space for the steadily growing org-mode  
> functionality. Always this create a lot of discussion since many  
> people familiar with the old bindings already even if the seems to  
> be sub-optimal now.
>
> I just wonder, would it make sense to add a chapter 0 to the org- 
> mode manual and/or a dedicated page at a prominent place on worg  
> which depicts only those key-binding changes from release version to  
> release version.
> I just think about the changes which affect peoples daily work  
> directly maybe without warnings. That means from a standard  
> changelog, exclude new features, nothing about internal changes, no  
> bugfix reports etc.. By this way this list should be rather small  
> but very important for (long-time) org-mode users.
> It is not enjoyable to find out in the middle of a "I just like to  
> finish it and come to the meeting in a second .... " time-frame that  
> things change during the last update. Emacs and org-mode make use  
> of  8 fingers and 2 thumbs without much visual feedback. Therefore,  
> most user use key-bindings in a heart-beating, breathing way without  
> thinking about it. Might be a good idea if there is a central place  
> to tell them to fight mentally for a while against there  
> subconscious or reconfigure it as they like.
>
> Just an idea.
>
> Regards
>
> Torsten
>
> BTW. I noticed that "[Orgmode]" is not added automatically to the  
> subject. Is this a feature or a bug :) ? I know from other mail- 
> lists that this is done automatically.
>
> _______________________________________________
> Emacs-orgmode mailing list
> Remember: use `Reply All' to send replies to the list.
> Emacs-orgmode@gnu.org
> http://lists.gnu.org/mailman/listinfo/emacs-orgmode

- Carsten

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2009-11-07  6:40 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2009-11-06 16:25 Is there a prominent place to announce user-interface changes ? Torsten Wagner
2009-11-07  6:40 ` Carsten Dominik

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