bug#13566: 24.1; Too easy to forget things with remember

bug#13566: 24.1; Too easy to forget things with remember

[Reuben Thomas]

The *Remember* buffer, as a non-file-visiting buffer, does not cause a
prompt when you kill it or exit Emacs with the contents unsaved. This is
unfortunate: I just lost 15 minutes’ work when I hit C-x C-c in
remember-mode by mistake instead of C-c C-c.

I can fix this particular problem by adding

(lambda nil (setq buffer-offer-save t))

to remember-mode-hook, but shouldn't this be the default behavior? Also,
it doesn't help with hitting C-x k RET by mistake in a remember-mode
buffer.

Since pretty much by definition the user has entered remember-mode in
order to write something that will be saved, maybe this is worth fixing?


In GNU Emacs 24.1.1 (x86_64-pc-linux-gnu, GTK+ Version 2.24.12)
 of 2012-09-22 on batsu, modified by Debian
Windowing system distributor `The X.Org Foundation', version 11.0.11300000
Configured using:
 `configure '--build' 'x86_64-linux-gnu' '--build' 'x86_64-linux-gnu'
 '--prefix=/usr' '--sharedstatedir=/var/lib' '--libexecdir=/usr/lib'
 '--localstatedir=/var/lib' '--infodir=/usr/share/info'
 '--mandir=/usr/share/man' '--with-pop=yes'
 '--enable-locallisppath=/etc/emacs24:/etc/emacs:/usr/local/share/emacs/24.1/site-lisp:/usr/local/share/emacs/site-lisp:/usr/share/emacs/24.1/site-lisp:/usr/share/emacs/site-lisp'
 '--with-crt-dir=/usr/lib/x86_64-linux-gnu' '--with-x=yes'
 '--with-x-toolkit=gtk' '--with-toolkit-scroll-bars'
 'build_alias=x86_64-linux-gnu' 'CFLAGS=-g -O2 -fstack-protector
 --param=ssp-buffer-size=4 -Wformat -Werror=format-security -Wall -O2'
 'CPPFLAGS=-D_FORTIFY_SOURCE=2''

Important settings:
  value of $LC_ALL: nil
  value of $LC_COLLATE: nil
  value of $LC_CTYPE: nil
  value of $LC_MESSAGES: nil
  value of $LC_MONETARY: en_GB.UTF-8
  value of $LC_NUMERIC: en_GB.UTF-8
  value of $LC_TIME: en_GB.UTF-8
  value of $LANG: en_GB.UTF-8
  value of $XMODIFIERS: nil
  locale-coding-system: utf-8-unix
  default enable-multibyte-characters: t

Major mode: Help

Minor modes in effect:
  recentf-mode: t
  show-paren-mode: t
  server-mode: t
  savehist-mode: t
  minibuffer-electric-default-mode: t
  iswitchb-mode: t
  icomplete-mode: t
  global-auto-revert-mode: t
  desktop-save-mode: t
  TeX-PDF-mode: t
  TeX-source-correlate-mode: t
  tooltip-mode: t
  mouse-wheel-mode: t
  file-name-shadow-mode: t
  global-font-lock-mode: t
  font-lock-mode: t
  blink-cursor-mode: t
  auto-composition-mode: t
  auto-encryption-mode: t
  auto-compression-mode: t
  column-number-mode: t
  line-number-mode: t
  transient-mark-mode: t

Recent input:
u f f e r <return> C-e C-b C-b C-b C-b C-x 0 <down-mouse-1> 
<mouse-1> C-h v n o t - 0 <backspace> <backspace> o 
<backspace> - t o - C-g <down-mouse-1> <mouse-1> M-x 
<up> <return> d f j s d l f k j s d f l k s d j f M-x 
C-g C-h v b u f f e r - m o d i f i e d <M-backspace> 
<M-backspace> C-g C-a C-x k <return> M-x b u f f e 
r - c r e a t e <backspace> <backspace> <backspace> 
<backspace> <backspace> <backspace> <backspace> <backspace> 
<backspace> <backspace> <backspace> <backspace> <backspace> 
<backspace> <backspace> <backspace> <backspace> <backspace> 
g e t - b u f i f <backspace> <backspace> f e r M-: 
( b <backspace> g e t - b u f f e r - f <backspace> 
c r e a t e SPC " f o o " ) <return> C-g C-g C-g C-x 
b f o i <backspace> o C-s <return> s d f l k j s l 
d k f j s l d f j C-x k <return> <down-mouse-1> <mouse-1> 
M-x r e m e m b e r - <backspace> C-g M-x c u s t o 
m i z e - v a r i a b l e <return> <up> <up> <up> <up> 
<up> <return> C-o C-g C-x o M-x r e m m b <backspace> 
e <backspace> <backspace> e m b e r - C-g M-x d p o 
d <backspace> <backspace> <backspace> <backspace> r 
e p o r t - e m c a s - b u <backspace> <backspace> 
<backspace> <backspace> <backspace> <backspace> c a 
s - b u <backspace> <backspace> <backspace> <backspace> 
<backspace> <backspace> a c s - b u g <return>

Recent messages:
Quit [2 times]
delete-backward-char: Text is read-only [5 times]
Quit
#<buffer foo>
Quit [4 times]
Creating customization items...
Creating customization items ...done
Resetting customization items...done
Creating customization setup...done
widget-before-change: Text is read-only: "Attempt to change text outside editable field"
Quit [2 times]

Load-path shadows:
/home/rrt/local/share/emacs/site-lisp/browse-kill-ring hides /usr/share/emacs24/site-lisp/emacs-goodies-el/browse-kill-ring
/home/rrt/local/share/emacs/site-lisp/dict hides /usr/share/emacs24/site-lisp/emacs-goodies-el/dict
/home/rrt/.emacs.d/elpa/dictionary-1.8.7/dictionary-init hides /usr/share/emacs24/site-lisp/dictionary-el/dictionary-init
/home/rrt/.emacs.d/elpa/dictionary-1.8.7/dictionary hides /usr/share/emacs24/site-lisp/dictionary-el/dictionary
/home/rrt/.emacs.d/elpa/dictionary-1.8.7/link hides /usr/share/emacs24/site-lisp/dictionary-el/link
/home/rrt/.emacs.d/elpa/dictionary-1.8.7/connection hides /usr/share/emacs24/site-lisp/dictionary-el/connection
/usr/share/emacs24/site-lisp/auctex/tex-style hides /usr/share/emacs/site-lisp/auctex/tex-style
/usr/share/emacs24/site-lisp/auctex/tex-mik hides /usr/share/emacs/site-lisp/auctex/tex-mik
/usr/share/emacs24/site-lisp/auctex/multi-prompt hides /usr/share/emacs/site-lisp/auctex/multi-prompt
/usr/share/emacs24/site-lisp/auctex/tex-jp hides /usr/share/emacs/site-lisp/auctex/tex-jp
/usr/share/emacs24/site-lisp/auctex/tex-info hides /usr/share/emacs/site-lisp/auctex/tex-info
/usr/share/emacs24/site-lisp/auctex/plain-tex hides /usr/share/emacs/site-lisp/auctex/plain-tex
/usr/share/emacs24/site-lisp/auctex/latex hides /usr/share/emacs/site-lisp/auctex/latex
/usr/share/emacs24/site-lisp/auctex/preview hides /usr/share/emacs/site-lisp/auctex/preview
/usr/share/emacs24/site-lisp/auctex/tex hides /usr/share/emacs/site-lisp/auctex/tex
/usr/share/emacs24/site-lisp/auctex/texmathp hides /usr/share/emacs/site-lisp/auctex/texmathp
/usr/share/emacs24/site-lisp/auctex/context-nl hides /usr/share/emacs/site-lisp/auctex/context-nl
/usr/share/emacs24/site-lisp/auctex/tex-font hides /usr/share/emacs/site-lisp/auctex/tex-font
/usr/share/emacs24/site-lisp/auctex/toolbar-x hides /usr/share/emacs/site-lisp/auctex/toolbar-x
/usr/share/emacs24/site-lisp/auctex/tex-buf hides /usr/share/emacs/site-lisp/auctex/tex-buf
/usr/share/emacs24/site-lisp/auctex/bib-cite hides /usr/share/emacs/site-lisp/auctex/bib-cite
/usr/share/emacs24/site-lisp/auctex/context-en hides /usr/share/emacs/site-lisp/auctex/context-en
/usr/share/emacs24/site-lisp/auctex/tex-fold hides /usr/share/emacs/site-lisp/auctex/tex-fold
/usr/share/emacs24/site-lisp/auctex/tex-bar hides /usr/share/emacs/site-lisp/auctex/tex-bar
/usr/share/emacs24/site-lisp/auctex/context hides /usr/share/emacs/site-lisp/auctex/context
/usr/share/emacs24/site-lisp/auctex/prv-emacs hides /usr/share/emacs/site-lisp/auctex/prv-emacs
/usr/share/emacs24/site-lisp/auctex/font-latex hides /usr/share/emacs/site-lisp/auctex/font-latex
/usr/share/emacs/site-lisp/golang-mode/go-mode-load hides /usr/share/emacs/24.1/site-lisp/golang-mode/go-mode-load
/usr/share/emacs/site-lisp/golang-mode/go-mode hides /usr/share/emacs/24.1/site-lisp/golang-mode/go-mode
/usr/share/emacs/24.1/site-lisp/cmake-data/cmake-mode hides /usr/share/emacs/site-lisp/cmake-mode
/usr/share/emacs/24.1/site-lisp/cdargs hides /usr/share/emacs/site-lisp/cdargs
/usr/share/emacs/site-lisp/rst hides /usr/share/emacs/24.1/lisp/textmodes/rst
/usr/share/emacs24/site-lisp/dictionaries-common/ispell hides /usr/share/emacs/24.1/lisp/textmodes/ispell
/usr/share/emacs24/site-lisp/dictionaries-common/flyspell hides /usr/share/emacs/24.1/lisp/textmodes/flyspell

Features:
(shadow sort mail-extr emacsbug message format-spec rfc822 mml mml-sec
mm-decode mm-bodies mm-encode mail-parse rfc2231 mailabbrev gmm-utils
mailheader sendmail rfc2047 rfc2045 ietf-drums mail-utils cus-edit
multi-isearch pp help-mode view texmathp remember lua-mode cperl-mode
latexenc todoo vc-git preview prv-emacs noutline outline tex-buf
font-latex latex tex-style flymake compile comint ansi-color ring
face-remap flyspell ispell smart-quotes jka-compr
auto-dictionary-autoloads c-eldoc-autoloads dictionary-autoloads
diff-git-autoloads dired-isearch-autoloads full-ack-autoloads
guess-style-autoloads kill-ring-search-autoloads magit-autoloads
mv-shell-autoloads tumble-autoloads http-post-simple-autoloads package
tabulated-list completing-help recentf tree-widget wid-edit uniquify
paren server savehist minibuf-eldef iswitchb icomplete autorevert
desktop cus-start cus-load ropemacs pymacs warnings url-util url-parse
auth-source eieio byte-opt bytecomp byte-compile cconv macroexp
gnus-util password-cache url-vars mm-util mail-prsvr tex dbus xml
regexp-opt user-site-loaddefs advice advice-preload yasnippet help-fns
derived edmacro kmacro easymenu assoc cl muse-autoloads go-mode-load
emacs-goodies-el emacs-goodies-custom emacs-goodies-loaddefs easy-mmode
preview-latex tex-site auto-loads time-date tooltip ediff-hook vc-hooks
lisp-float-type mwheel x-win x-dnd tool-bar dnd fontset image fringe
lisp-mode register page menu-bar rfn-eshadow timer select scroll-bar
mouse jit-lock font-lock syntax facemenu font-core frame cham georgian
utf-8-lang misc-lang vietnamese tibetan thai tai-viet lao korean
japanese hebrew greek romanian slovak czech european ethiopic indian
cyrillic chinese case-table epa-hook jka-cmpr-hook help simple abbrev
minibuffer loaddefs button faces cus-face files text-properties overlay
sha1 md5 base64 format env code-pages mule custom widget
hashtable-print-readable backquote make-network-process dbusbind
dynamic-setting system-font-setting font-render-setting move-toolbar gtk
x-toolkit x multi-tty emacs)

-- 
http://rrt.sc3d.org/

bug#13566: 24.1; Too easy to forget things with remember

[Glenn Morris]

Reuben Thomas wrote:

> The *Remember* buffer, as a non-file-visiting buffer, does not cause a
> prompt when you kill it or exit Emacs with the contents unsaved. This is
> unfortunate: I just lost 15 minutes' work when I hit C-x C-c in
> remember-mode by mistake instead of C-c C-c.
>
> I can fix this particular problem by adding
>
> (lambda nil (setq buffer-offer-save t))
>
> to remember-mode-hook, but shouldn't this be the default behavior?

Sounds right, please apply.
Or maybe (I don't use remember) you want to add remember-finalize to
kill-emacs-hook or kill-emacs-query-functions.

bug#13566: 24.1; Too easy to forget things with remember

[Reuben Thomas]

[-- Attachment #1: Type: text/plain, Size: 963 bytes --]

On 14 May 2013 08:42, Glenn Morris <rgm@gnu.org> wrote:

> Reuben Thomas wrote:
>
> > The *Remember* buffer, as a non-file-visiting buffer, does not cause a
> > prompt when you kill it or exit Emacs with the contents unsaved. This is
> > unfortunate: I just lost 15 minutes' work when I hit C-x C-c in
> > remember-mode by mistake instead of C-c C-c.
> >
> > I can fix this particular problem by adding
> >
> > (lambda nil (setq buffer-offer-save t))
> >
> > to remember-mode-hook, but shouldn't this be the default behavior?
>
> Sounds right, please apply.
> Or maybe (I don't use remember) you want to add remember-finalize to
> kill-emacs-hook or kill-emacs-query-functions.
>

It seems to me that it's more consistent to make Emacs prompt to save the
remember buffer, as it does for other unsaved buffers (the alternative
suggested here would make Emacs silently save the remember buffer if
exited), but I'd appreciate some guidance.

-- 
http://rrt.sc3d.org

[-- Attachment #2: Type: text/html, Size: 1450 bytes --]

bug#13566: 24.1; Too easy to forget things with remember

[Sebastien Vauban]

Hello,

Reuben Thomas wrote:
> On 14 May 2013 08:42, Glenn Morris <rgm-mXXj517/zsQ@public.gmane.org> wrote:
>> Reuben Thomas wrote:
>>
>> > The *Remember* buffer, as a non-file-visiting buffer, does not cause a
>> > prompt when you kill it or exit Emacs with the contents unsaved. This is
>> > unfortunate: I just lost 15 minutes' work when I hit C-x C-c in
>> > remember-mode by mistake instead of C-c C-c.
>> >
>> > I can fix this particular problem by adding
>> >
>> > (lambda nil (setq buffer-offer-save t))
>> >
>> > to remember-mode-hook, but shouldn't this be the default behavior?
>>
>> Sounds right, please apply.
>> Or maybe (I don't use remember) you want to add remember-finalize to
>> kill-emacs-hook or kill-emacs-query-functions.
>>
>
> It seems to me that it's more consistent to make Emacs prompt to save the
> remember buffer, as it does for other unsaved buffers (the alternative
> suggested here would make Emacs silently save the remember buffer if
> exited), but I'd appreciate some guidance.

Please note that `remember' has been replaced by `org-capture', at least if we
speak of the same...

Best regards,
  Seb

-- 
Sebastien Vauban

bug#13566: 24.1; Too easy to forget things with remember

[Reuben Thomas]

[-- Attachment #1: Type: text/plain, Size: 1592 bytes --]

On 14 May 2013 14:22, Sebastien Vauban <sva-news@mygooglest.com> wrote:

> Hello,
>
> Reuben Thomas wrote:
> > On 14 May 2013 08:42, Glenn Morris <rgm@gnu.org> wrote:
> >> Reuben Thomas wrote:
> >>
> >> > The *Remember* buffer, as a non-file-visiting buffer, does not cause a
> >> > prompt when you kill it or exit Emacs with the contents unsaved. This
> is
> >> > unfortunate: I just lost 15 minutes' work when I hit C-x C-c in
> >> > remember-mode by mistake instead of C-c C-c.
> >> >
> >> > I can fix this particular problem by adding
> >> >
> >> > (lambda nil (setq buffer-offer-save t))
> >> >
> >> > to remember-mode-hook, but shouldn't this be the default behavior?
> >>
> >> Sounds right, please apply.
> >> Or maybe (I don't use remember) you want to add remember-finalize to
> >> kill-emacs-hook or kill-emacs-query-functions.
> >>
> >
> > It seems to me that it's more consistent to make Emacs prompt to save the
> > remember buffer, as it does for other unsaved buffers (the alternative
> > suggested here would make Emacs silently save the remember buffer if
> > exited), but I'd appreciate some guidance.
>
> Please note that `remember' has been replaced by `org-capture', at least
> if we
> speak of the same...
>

I think you mean "superseded", not "replaced": remember.el is still in
Emacs bazaar. Yes, I'm aware of it, but presumably as long as remember.el
is still included with Emacs it's acceptable to fix bugs in it? And since
org-capture is not, as far as I know, based on remember, there is no reason
to suspect that bugs in remember will be mirrored in org-capture?

[-- Attachment #2: Type: text/html, Size: 2319 bytes --]

bug#13566: 24.1; Too easy to forget things with remember

[Sebastien Vauban]

Reuben Thomas wrote:
> On 14 May 2013 14:22, Sebastien Vauban <sva-news-D0wtAvR13HarG/iDocfnWg@public.gmane.org> wrote:
>> Reuben Thomas wrote:
>>> On 14 May 2013 08:42, Glenn Morris <rgm-mXXj517/zsQ@public.gmane.org> wrote:
>>>> Reuben Thomas wrote:
>>>>
>>>>> The *Remember* buffer, as a non-file-visiting buffer, does not cause a
>>>>> prompt when you kill it or exit Emacs with the contents unsaved. This is
>>>>> unfortunate: I just lost 15 minutes' work when I hit C-x C-c in
>>>>> remember-mode by mistake instead of C-c C-c.
>>>>>
>>>>> I can fix this particular problem by adding
>>>>>
>>>>> (lambda nil (setq buffer-offer-save t))
>>>>>
>>>>> to remember-mode-hook, but shouldn't this be the default behavior?
>>>>
>>>> Sounds right, please apply.
>>>> Or maybe (I don't use remember) you want to add remember-finalize to
>>>> kill-emacs-hook or kill-emacs-query-functions.
>>>
>>> It seems to me that it's more consistent to make Emacs prompt to save the
>>> remember buffer, as it does for other unsaved buffers (the alternative
>>> suggested here would make Emacs silently save the remember buffer if
>>> exited), but I'd appreciate some guidance.
>>
>> Please note that `remember' has been replaced by `org-capture', at least if
>> we speak of the same...
>
> I think you mean "superseded", not "replaced":

Yes, you're right.

> remember.el is still in Emacs bazaar. Yes, I'm aware of it, but presumably
> as long as remember.el is still included with Emacs it's acceptable to fix
> bugs in it? And since org-capture is not, as far as I know, based on
> remember, there is no reason to suspect that bugs in remember will be
> mirrored in org-capture?

I just wanted to direct you toward a better and more recent implementation.
But, sure, if you use the other one, and it's buggy, it should be fixed, as
long it's still around, in the official code base.

Best regards,
  Seb

-- 
Sebastien Vauban

bug#13566: 24.1; Too easy to forget things with remember

[Reuben Thomas]

[-- Attachment #1: Type: text/plain, Size: 501 bytes --]

On 14 May 2013 15:57, Sebastien Vauban <sva-news@mygooglest.com> wrote:

> I just wanted to direct you toward a better and more recent implementation.
> But, sure, if you use the other one, and it's buggy, it should be fixed, as
> long it's still around, in the official code base.
>

You're quite right, and indeed I did try capture some time ago, couldn't
immediately make it do what I wanted, and left a FIXME in my Emacs setup to
return to the problem at some later date.

-- 
http://rrt.sc3d.org

[-- Attachment #2: Type: text/html, Size: 900 bytes --]

bug#13566: 24.1; Too easy to forget things with remember

[Sebastien Vauban]

Reuben Thomas wrote:
> On 14 May 2013 15:57, Sebastien Vauban <sva-news-D0wtAvR13HarG/iDocfnWg@public.gmane.org> wrote:
>
>> I just wanted to direct you toward a better and more recent implementation.
>> But, sure, if you use the other one, and it's buggy, it should be fixed, as
>> long it's still around, in the official code base.
>
> You're quite right, and indeed I did try capture some time ago, couldn't
> immediately make it do what I wanted, and left a FIXME in my Emacs setup to
> return to the problem at some later date.

IIRC, I just used `org-capture-import-remember-templates', and that was it!

Best regards,
  Seb

-- 
Sebastien Vauban

bug#13566: 24.1; Too easy to forget things with remember

[Glenn Morris]

Reuben Thomas wrote:

> It seems to me that it's more consistent to make Emacs prompt to save the
> remember buffer, as it does for other unsaved buffers (the alternative
> suggested here would make Emacs silently save the remember buffer if
> exited), but I'd appreciate some guidance.

Maybe you want to associate it with a real file name?
Then it will get auto-save protection, etc.
Probably some temp-name (so that multiple instances do not clash) in
~/.emacs.d, that gets deleted when you call remember-finalize?

bug#13566: 24.1; Too easy to forget things with remember

[Reuben Thomas]

[-- Attachment #1: Type: text/plain, Size: 1157 bytes --]

On 14 May 2013 16:54, Glenn Morris <rgm@gnu.org> wrote:

> Reuben Thomas wrote:
>
> > It seems to me that it's more consistent to make Emacs prompt to save the
> > remember buffer, as it does for other unsaved buffers (the alternative
> > suggested here would make Emacs silently save the remember buffer if
> > exited), but I'd appreciate some guidance.
>
> Maybe you want to associate it with a real file name?
> Then it will get auto-save protection, etc.
> Probably some temp-name (so that multiple instances do not clash) in
> ~/.emacs.d, that gets deleted when you call remember-finalize?
>

Thanks for the extra suggestion.

Auto-save protection would be nice, but that seems like a separate issue,
unless you're also suggesting that the prompt-on-exit for an unfinalized
remember buffer should be to save in a temporary file (which could be
confusing, especially for a user who doesn't use desktop.el or some other
session support), in which case I'm not sure it's a good idea.

In any case, as Sebastian has pointed out, remember is effectively
obsolescent; this sounds like it might be over-complicated for a minimal
fix.

-- 
http://rrt.sc3d.org

[-- Attachment #2: Type: text/html, Size: 1760 bytes --]

bug#13566: 24.1; Too easy to forget things with remember

[Glenn Morris]

Reuben Thomas wrote:

> Auto-save protection would be nice, but that seems like a separate issue,
> unless you're also suggesting that the prompt-on-exit for an unfinalized
> remember buffer should be to save in a temporary file (which could be
> confusing, especially for a user who doesn't use desktop.el or some other
> session support), in which case I'm not sure it's a good idea.

Maybe use write-contents-functions to make saving actually finalize.

> In any case, as Sebastian has pointed out, remember is effectively
> obsolescent; this sounds like it might be over-complicated for a minimal
> fix.

It's a shame to see existing small functionality reimplemented by a
mammoth package. But if no-one cares enough to do anything about it,
that's how it is I suppose.

bug#13566: 24.1; Too easy to forget things with remember

[Reuben Thomas]

[-- Attachment #1: Type: text/plain, Size: 1190 bytes --]

On 14 May 2013 17:14, Glenn Morris <rgm@gnu.org> wrote:

> Reuben Thomas wrote:
>
> > Auto-save protection would be nice, but that seems like a separate issue,
> > unless you're also suggesting that the prompt-on-exit for an unfinalized
> > remember buffer should be to save in a temporary file (which could be
> > confusing, especially for a user who doesn't use desktop.el or some other
> > session support), in which case I'm not sure it's a good idea.
>
> Maybe use write-contents-functions to make saving actually finalize.
>

Could you summarize what you're suggesting now, please? I previously
suggested one change, to add (setq buffer-offer-save t) to the function
"remember". Your suggestions taken together seem to involve multiple
changes to achieve a) the same result as mine and b) auto-save protection,
which seems worthwhile if it's similarly simple.


>  It's a shame to see existing small functionality reimplemented by a
> mammoth package. But if no-one cares enough to do anything about it,
> that's how it is I suppose.
>

I'm not sure it makes a lot of difference if org-capture is as simple to
use, since org-mode is shipped as part of Emacs.

-- 
http://rrt.sc3d.org

[-- Attachment #2: Type: text/html, Size: 1928 bytes --]

bug#13566: 24.1; Too easy to forget things with remember

[Glenn Morris]

Reuben Thomas wrote:

> Could you summarize what you're suggesting now, please? I previously
> suggested one change, to add (setq buffer-offer-save t) to the function
> "remember". 

Which I said was fine, and that you should install.
If you think nothing more is needed, please install it and close this.

bug#13566: 24.1; Too easy to forget things with remember

[Reuben Thomas]

[-- Attachment #1: Type: text/plain, Size: 535 bytes --]

On 14 May 2013 18:10, Glenn Morris <rgm@gnu.org> wrote:

> Reuben Thomas wrote:
>
> > Could you summarize what you're suggesting now, please? I previously
> > suggested one change, to add (setq buffer-offer-save t) to the function
> > "remember".
>
> Which I said was fine, and that you should install.
> If you think nothing more is needed, please install it and close this.
>

Thanks, will do. Thank you also for your additional suggestions: it was
useful to have alternatives with which to compare my idea.

-- 
http://rrt.sc3d.org

[-- Attachment #2: Type: text/html, Size: 1009 bytes --]

bug#13566: 24.1; Too easy to forget things with remember

[Reuben Thomas]

[-- Attachment #1: Type: text/plain, Size: 847 bytes --]

On 14 May 2013 19:10, Reuben Thomas <rrt@sc3d.org> wrote:

>
> On 14 May 2013 18:10, Glenn Morris <rgm@gnu.org> wrote:
>
>> Reuben Thomas wrote:
>>
>> > Could you summarize what you're suggesting now, please? I previously
>> > suggested one change, to add (setq buffer-offer-save t) to the function
>> > "remember".
>>
>> Which I said was fine, and that you should install.
>> If you think nothing more is needed, please install it and close this.
>>
>
> Thanks, will do. Thank you also for your additional suggestions: it was
> useful to have alternatives with which to compare my idea.
>

Apologies, I think I've messed up the commit, and pushed a change with an
empty log message (finger trouble: I hit C-c C-c and committed instead of
C-c C-a to pull in the changelog message).

Is there some way to fix this mistake?

-- 
http://rrt.sc3d.org

[-- Attachment #2: Type: text/html, Size: 1766 bytes --]

bug#13566: 24.1; Too easy to forget things with remember

[Reuben Thomas]

[-- Attachment #1: Type: text/plain, Size: 1381 bytes --]

On 14 May 2013 20:53, Reuben Thomas <rrt@sc3d.org> wrote:

>
> On 14 May 2013 19:10, Reuben Thomas <rrt@sc3d.org> wrote:
>
>>
>> On 14 May 2013 18:10, Glenn Morris <rgm@gnu.org> wrote:
>>
>>> Reuben Thomas wrote:
>>>
>>> > Could you summarize what you're suggesting now, please? I previously
>>> > suggested one change, to add (setq buffer-offer-save t) to the function
>>> > "remember".
>>>
>>> Which I said was fine, and that you should install.
>>> If you think nothing more is needed, please install it and close this.
>>>
>>
>> Thanks, will do. Thank you also for your additional suggestions: it was
>> useful to have alternatives with which to compare my idea.
>>
>
> Apologies, I think I've messed up the commit, and pushed a change with an
> empty log message (finger trouble: I hit C-c C-c and committed instead of
> C-c C-a to pull in the changelog message).
>
> Is there some way to fix this mistake?
>

(I tried to uncommit and recommit, but the bug number was no longer
recognized. I guess also that would have rewritten the history of the
public repository, not a good idea. But since a commit that refers to a
non-existent bug can automatically refused, could commits with empty log
messages also be automatically refused? This would especially help hackers
more accustomed, like me, to git, which refuses empty commit messages by
default.)

-- 
http://rrt.sc3d.org

[-- Attachment #2: Type: text/html, Size: 2721 bytes --]

bug#13566: Commit made

[Reuben Thomas]

[-- Attachment #1: Type: text/plain, Size: 276 bytes --]

I'm not sure what happened, but my commit did not seem to stick. I've just
made it again. As before, bzr refuses to hear about my reference to the bug
number, since it's already closed, so I hereby state that the bug is closed
by commit revno 114702.

-- 
http://rrt.sc3d.org

[-- Attachment #2: Type: text/html, Size: 380 bytes --]

bug#13566: Commit made

[Glenn Morris]

Reuben Thomas wrote:

> I'm not sure what happened, but my commit did not seem to stick. I've just
> made it again. As before, bzr refuses to hear about my reference to the bug
> number, since it's already closed, so I hereby state that the bug is closed
> by commit revno 114702.

(Sorry, I missed the prior mails.)

FYI, you haven't committed anything to Savannah. Also this bug report is
still open. To close it, you would send mail to 13566-done@debbugs.

(Bzr has no knowledge of/interest in/control over whether a bug is
opened or closed, so I don't understand what you are saying.)

bug#13566: Commit made

[Stefan Monnier]

> I'm not sure what happened, but my commit did not seem to stick.

What makes you think so?
What command have you executed, what results did you get?
You know, the usual bug-report routine,


        Stefan

bug#13566: Commit made

[Reuben Thomas]

[-- Attachment #1: Type: text/plain, Size: 461 bytes --]

On 18 October 2013 03:57, Stefan Monnier <monnier@iro.umontreal.ca> wrote:

> > I'm not sure what happened, but my commit did not seem to stick.
>
> What makes you think so?
>

It did not appear on Savannah.

What command have you executed, what results did you get?
> You know, the usual bug-report routine,
>

I did not attempt to report a bug, since instead I redid the process. I'm
sure I did something wrong, and there was no bug.

-- 
http://rrt.sc3d.org

[-- Attachment #2: Type: text/html, Size: 1033 bytes --]

bug#13566: Commit made

[Stefan Monnier]

>> > I'm not sure what happened, but my commit did not seem to stick.
>> What makes you think so?
> It did not appear on Savannah.
>> What command have you executed, what results did you get?
>> You know, the usual bug-report routine,
> I did not attempt to report a bug, since instead I redid the process.
> I'm sure I did something wrong, and there was no bug.

Many bug-reports are like that.  The same info is needed to help you
find the part that was wrong.


        Stefan

bug#13566: Commit made

[Reuben Thomas]

[-- Attachment #1: Type: text/plain, Size: 789 bytes --]

On 18 October 2013 13:59, Stefan Monnier <monnier@iro.umontreal.ca> wrote:

> >> > I'm not sure what happened, but my commit did not seem to stick.
> >> What makes you think so?
> > It did not appear on Savannah.
> >> What command have you executed, what results did you get?
> >> You know, the usual bug-report routine,
> > I did not attempt to report a bug, since instead I redid the process.
> > I'm sure I did something wrong, and there was no bug.
>
> Many bug-reports are like that.  The same info is needed to help you
> find the part that was wrong.
>

Since I didn't realise something had gone wrong until some months later, it
seemed more profitable simply to redo than to attempt to reconstruct what I
did wrong on this occasion; but I take your point.

-- 
http://rrt.sc3d.org

[-- Attachment #2: Type: text/html, Size: 1263 bytes --]