lib.h File Reference

Compressed mbox local mailbox type. More...

#include <stdbool.h>
#include <stdio.h>
#include "core/lib.h"

Include dependency graph for lib.h:

This graph shows which files directly or indirectly include this file:

Go to the source code of this file.

Data Structures
struct	CompressInfo
	Private data for compress. More...

Functions
void	mutt_comp_init (void)
	Setup feature commands.
bool	mutt_comp_can_append (struct Mailbox *m)
	Can we append to this path?
bool	mutt_comp_can_read (const char *path)
	Can we read from this file?
int	mutt_comp_valid_command (const char *cmd)
	Is this command string allowed?

Variables
const struct MxOps	MxCompOps
	Compressed Mailbox - Implements MxOps -.

Detailed Description

Compressed mbox local mailbox type.

Authors

• Alain Penders
• Richard Russon

Copyright

This program is free software: you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation, either version 2 of the License, or (at your option) any later version.

This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details.

You should have received a copy of the GNU General Public License along with this program. If not, see http://www.gnu.org/licenses/.

Definition in file lib.h.

Function Documentation

mutt_comp_init()

void mutt_comp_init

(

void

)

Setup feature commands.

Definition at line 73 of file compress.c.

{
  commands_register(CompCommands, mutt_array_size(CompCommands));
}

Here is the call graph for this function:

Here is the caller graph for this function:

mutt_comp_can_append()

bool mutt_comp_can_append

(

struct Mailbox *

m

)

Can we append to this path?

Parameters

m

Mailbox

Return values

true	Yes, we can append to the file
false	No, appending isn't possible

To append to a file we can either use an 'append-hook' or a combination of 'open-hook' and 'close-hook'.

A match means it's our responsibility to append to the file.

Definition at line 367 of file compress.c.

{
  if (!m)
    return false;
 
  /* If this succeeds, we know there's an open-hook */
  struct CompressInfo *ci = set_compress_info(m);
  if (!ci)
    return false;
 
  /* We have an open-hook, so to append we need an append-hook,
   * or a close-hook. */
  if (ci->cmd_append || ci->cmd_close)
    return true;
 
  mutt_error(_("Can't append without an append-hook or close-hook : %s"), mailbox_path(m));
  return false;
}

Here is the call graph for this function:

Here is the caller graph for this function:

mutt_comp_can_read()

bool mutt_comp_can_read

(

const char *

path

)

Can we read from this file?

Parameters

path	Pathname of file to be tested

Return values

true	Yes, we can read the file
false	No, we can't read the file

Search for an 'open-hook' with a regex that matches the path.

A match means it's our responsibility to open the file.

Definition at line 396 of file compress.c.

{
  if (!path)
    return false;
 
  if (mutt_find_hook(MUTT_OPEN_HOOK, path))
    return true;
 
  return false;
}

Here is the call graph for this function:

Here is the caller graph for this function:

mutt_comp_valid_command()

int mutt_comp_valid_command

(

const char *

cmd

)

Is this command string allowed?

Parameters

cmd	Command string

Return values

1	Valid command
0	"%f" and/or "%t" is missing

A valid command string must have both "%f" (from file) and "%t" (to file). We don't check if we can actually run the command.

Definition at line 416 of file compress.c.

{
  if (!cmd)
    return 0;
 
  return strstr(cmd, "%f") && strstr(cmd, "%t");
}

Here is the caller graph for this function: