Re: send(1) and Draft-Folder.
Hi David, > > Ralph wrote: > > > > Draft-Folder: To specify the default draftfolder > > > > > > > > Removing the hyphen from the second draft-folder helps associate > > > > it with the -draftfolder switch, I think. > > > > > > Is this equivalent? > > > > > > Draft-Folder: -draftfolder's default > > > > I don't like that, because then I have to figure out how -draftfolder > > fits in. > > I might have come across as harsh on that. I didn't find that. :-) I was just left a bit unclear on your point but I think it's that I might understand draft folders, from mh-draft(5), but not know about this command's -draftfolder, say, and so it adds another level of indirection to get to the answer. > In reality, I don't have a preference. Given its peers, e.g. whom(1)'s Path:To determine the user's nmh directory Draft-Folder:To specify the default draftfolder Aliasfile: For a default alias file postproc:Program to post the message it may as well be left alone. It looks like there could be a general sweep through them to make them more brief and simply refer to an option where applicable. So for those above, Path:The user's nmh directory Draft-Folder:-draftfolder's default Aliasfile: -alias's default postproc:A post(8)-like program which does the work This would make more sense if the man pages listed options rather than burying them in prose. -- Cheers, Ralph.
Re: send(1) and Draft-Folder.
I wrote: > Ralph wrote: > > Is this equivalent? > > > > Draft-Folder: -draftfolder's default > > I don't like that, because then I have to figure out how -draftfolder > fits in. I might have come across as harsh on that. In reality, I don't have a preference. David
Re: send(1) and Draft-Folder.
Ralph wrote: > Hi David, > > > How about changing all of these man page descriptions: > > > > Draft-Folder: To find the default draft-folder > > > > to: > > > > Draft-Folder: To specify the default draftfolder > > > > Removing the hyphen from the second draft-folder helps associate it > > with the -draftfolder switch, I think. > > Is this equivalent? > > Draft-Folder: -draftfolder's default I don't like that, because then I have to figure out how -draftfolder fits in. David
Re: send(1) and Draft-Folder.
Hi David, > How about changing all of these man page descriptions: > > Draft-Folder: To find the default draft-folder > > to: > > Draft-Folder: To specify the default draftfolder > > Removing the hyphen from the second draft-folder helps associate it > with the -draftfolder switch, I think. Is this equivalent? Draft-Folder: -draftfolder's default -- Cheers, Ralph.
Re: send(1) and Draft-Folder.
I wrote: > How about changing all of these man page descriptions: > > Draft-Folder: To find the default draft-folder > > to: > > Draft-Folder: To specify the default draftfolder I committed that. And the additions to the profile created by install-mh(1) to enable the draft folder facility. David
Re: send(1) and Draft-Folder.
I wrote: > Ralph wrote: > > > So as it stands, the bug is with the man page and Draft-Folder should be > > removed. > > I'm not so sure. I see use cases for Draft-Folder with comp and whom. > I don't with dist, forw, repl, and whatnow. Now I see. dist, forw, repl, and whatnow need to know where to put or find drafts. How about changing all of these man page descriptions: Draft-Folder: To find the default draft-folder to: Draft-Folder: To specify the default draftfolder Removing the hyphen from the second draft-folder helps associate it with the -draftfolder switch, I think. David
Re: send(1) and Draft-Folder.
Ralph wrote: > So as it stands, the bug is with the man page and Draft-Folder should be > removed. I'm not so sure. I see use cases for Draft-Folder with comp and whom. I don't with dist, forw, repl, and whatnow. And I'm not sure about send given this: send with no file argument will query whether the draft is the intended file, whereas -draft will suppress this question. So to send a draft from a draftfolder non-interactively, the user would have to use "send -draft -draftfolder drafts". That seems too cumbersome to me. There is a typo in the mh-draft man page: will construct the message draft in the ‘draft’ folder using the ‘new’ message number. should say 'drafts' folder given these example profile entries: Draft−Folder: drafts sendf: −draftfolder +drafts > This is a perennial problem. I normally bring up Python's ‘from future > import ...’ method of requesting new behaviour. I don't think the benefits are worth the trouble we'd face when diagnosing user problems. We'd have to figure out what behavior the asked for vs what they think they asked for. David
Re: send(1) and Draft-Folder.
Hi David, > > I've Draft-Folder set to drafts in .mh_profile. Using at(1) to > > ‘send 42’ fails because `mhpath +`/42 doesn't exist. > > Would it succeed with 'send -draftfolder drafts 42'? Yes, I've just tried ‘send -draftfolder drafts 42’ and it worked. > Or if your profile included '-draftfolder drafts' for a 'send' > component? I was about to add that originally when I wondered about Draft-Folder and noted the man page said it was used. > > The man page seems inconsistent. The default is -nodraftfolder so > > why is Draft-Folder listed under Profile Components as it isn't > > used? > > Yeah, this looks like an unfortuate result of tacking on the draft > folder facility, It would have been easier to have had that from the > beginning. And only used that, because the old-style simple draft > file isn't very useful with it. So as it stands, the bug is with the man page and Draft-Folder should be removed. > > I'd expect a .mh_profile Draft-Folder to be used by default. > > I agree. But I'm not sure if we want to change it at this point, to > not break existing users' workflows. This is a perennial problem. I normally bring up Python's ‘from future import ...’ method of requesting new behaviour. https://lists.nongnu.org/archive/html/nmh-workers/2014-08/msg00129.html ‘How about the opposite of Python's `from future import ...'? Have a ~/.mh_profile entry like `old-fogey' or `stuck-in-1989' as a global decision maker when code changes to support both old and new ways.’ https://lists.nongnu.org/archive/html/nmh-workers/2014-08/msg00089.html ‘Like Python's `from future import sanity'. ‘A problem with ~/.mh_profile calling for sanity is that it might be wanted generally but the user can't be sure no scripts they use want insanity?’ All ideas welcome, however daft. > For new users, install-mh could add a "Draft-Folder" component and add > a corresponding -draftfolder to a "send" component. That's an improvement on now. :-) -- Cheers, Ralph.
Re: send(1) and Draft-Folder.
Ralph wrote: > I've Draft-Folder set to drafts in .mh_profile. Using at(1) to ‘send > 42’ fails because `mhpath +`/42 doesn't exist. Would it succeed with 'send -draftfolder drafts 42'? Or if your profile included '-draftfolder drafts' for a 'send' component? > The man page seems inconsistent. The default is -nodraftfolder so why > is Draft-Folder listed under Profile Components as it isn't used? Yeah, this looks like an unfortuate result of tacking on the draft folder facility, It would have been easier to have had that from the beginning. And only used that, because the old-style simple draft file isn't very useful with it. > I'd expect a .mh_profile Draft-Folder to be used by default. I agree. But I'm not sure if we want to change it at this point, to not break existing users' workflows. For new users, install-mh could add a "Draft-Folder" component and add a corresponding -draftfolder to a "send" component. David
send(1) and Draft-Folder.
Hi, send [-help] [-version] [-alias aliasfile] [-draft] [-draftfolder +folder] [-draftmessage msg] [-nodraftfolder] ... The -draftfolder +folder and -draftmessage msg switches invoke the nmh draft folder facility. This is an advanced (and highly useful) feature. Consult mh-draft(5) for more information. PROFILE COMPONENTS ... Draft-Folder:To find the default draft-folder ... DEFAULTS ... `-nodraftfolder' I've Draft-Folder set to drafts in .mh_profile. Using at(1) to ‘send 42’ fails because `mhpath +`/42 doesn't exist. ‘send drafts/42’ does work. The man page seems inconsistent. The default is -nodraftfolder so why is Draft-Folder listed under Profile Components as it isn't used? I'd expect a .mh_profile Draft-Folder to be used by default. Correction welcome if I'm not understanding this. I don't use send(1) directly often, mainly just as ‘s’ from whatnow(1). -- Cheers, Ralph.
