Your message dated Thu, 26 Aug 2010 14:00:16 +0200
with message-id <[email protected]>
and subject line Re: Bug#594214: nanoblogger: creates empty entry on 
quit-no-write from editor
has caused the Debian Bug report #594214,
regarding nanoblogger: creates empty entry on quit-no-write from editor
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)


-- 
594214: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=594214
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: nanoblogger
Version: 3.3-4
Severity: normal

The following command sequence will cause a blank entry to appear.

----
nb -a -b $BLOGDIR
# configure if it's a new blog
nb -a -b $BLOGDIR # to add a new entry if the blog's new
# your editor's "quit without writing" command, like vi's ZQ
----

I have repeated this using nano, various *vi*, and mousepad. By the time
this reaches BTS, an example should be visible at [1].

[1] http://brianryans.beoch.net/bugs/nanoblogger/nbtest/

I'm developing a patch for it, but I'm not sure if it will cause
breakage yet. The patch would ideally compare the saved file to the
template, and reject the entry if they're the same.

-- System Information:
Debian Release: 5.0.5
  APT prefers stable
  APT policy: (750, 'stable'), (500, 'stable')
Architecture: i386 (i686)

Kernel: Linux 2.6.26-2-686 (SMP w/1 CPU core)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages nanoblogger depends on:
ii  bsdmainutils                  6.1.10     collection of more utilities from 

Versions of packages nanoblogger recommends:
ii  tidy                       20080116cvs-2 HTML syntax checker and reformatte

Versions of packages nanoblogger suggests:
ii  elinks [www-browser]    0.11.4-3         advanced text-mode WWW browser
ii  iceweasel [www-browser] 3.0.6-3          lightweight web browser based on M
ii  kazehakase [www-browser 0.5.4-2.2+lenny1 GTK+-base web browser that allows 
ii  lynx-cur [www-browser]  2.8.7dev9-2.1    Text-mode WWW Browser with NLS sup
ii  nanoblogger-extra       3.3-3            Nanoblogger plugins

-- no debconf information

-- 
 _  Brian Ryans 8B2A 54C4 E275 8CFD 8A7D 5D0B 0AD0 B014 C112 13D0     .
( ) ICQ UIN: 43190205 | Mail/MSN/Jabber: [email protected]       ..:
 X  ASCII Ribbon Campaign Against HTML mail and v-cards: asciiribbon.org
/ \ "The most powerful optimization tool . . . may be the Delete key."
                                                         -- Eric Raymond

Attachment: signature.asc
Description: Digital signature


--- End Message ---
--- Begin Message ---
Version: 3.4-1

Dne Tue, 24 Aug 2010 09:00:09 -0500
Brian Ryans <[email protected]> napsal(a):

> Package: nanoblogger
> Version: 3.3-4
> Severity: normal
> 
> The following command sequence will cause a blank entry to appear.
> 
> ----
> nb -a -b $BLOGDIR
> # configure if it's a new blog
> nb -a -b $BLOGDIR # to add a new entry if the blog's new
> # your editor's "quit without writing" command, like vi's ZQ
> ----
> 
> I have repeated this using nano, various *vi*, and mousepad. By the time
> this reaches BTS, an example should be visible at [1].
> 
> [1] http://brianryans.beoch.net/bugs/nanoblogger/nbtest/
> 
> I'm developing a patch for it, but I'm not sure if it will cause
> breakage yet. The patch would ideally compare the saved file to the
> template, and reject the entry if they're the same.

Since version 3.4 it waits for confirmation before actually adding an
entry, so it sort of fixes the problem (you have way to avoid creating
the blog entry).

-- 
        Michal Čihař | http://cihar.com | http://blog.cihar.com

Attachment: signature.asc
Description: PGP signature


--- End Message ---

Reply via email to